944 debugger problem

I submitted http://www.intellij.net/tracker/idea/viewSCR?publicId=17692
"Cannot expand frame/inspect nodes in debugger". I would have thought
this to be major a issue. But since nobody else has mentioned it I'm
wondering whether its just me. If it really is a problem, the please
ignore this post -- I know how to wait for the build. But if nobody else
is seeing this, I'd love to know so I track down whats different in my
environment.

thanks!

5 comments
Comment actions Permalink

I get this too. The reason I didn't say anything was that you'd already
posted it ;)

Yeah, it's frustrating; I have been stuck at 922 due to there being
serious debugger issues in every build since. I guess that maybe the
IDEA developers aren't using the debugger as much as everything else ;)

N.

Barry Kaplan wrote:

I submitted http://www.intellij.net/tracker/idea/viewSCR?publicId=17692
"Cannot expand frame/inspect nodes in debugger". I would have thought
this to be major a issue. But since nobody else has mentioned it I'm
wondering whether its just me. If it really is a problem, the please
ignore this post -- I know how to wait for the build. But if nobody else
is seeing this, I'd love to know so I track down whats different in my
environment.

thanks!


0
Comment actions Permalink

I just switched to 944 from 939. 944 gives this error when trying to debug Junit tests:
"local variable debug info unavailable".

I get a ClassNotFoundException at URLClassLoader.findClass(final String name) where name is com.intellij.rt.execution.junit2.JUnitStarter.

I do have "debug info" turned on in the compiler and I have cleared the cache.

Is my environment cursed, or has anyone got similar problems?

cheers,
Sakke

0
Comment actions Permalink

I have the same problem here (939 works). I've also cleared the cache but I still cannot debug. Running the prgram is no problem

Christian

0
Comment actions Permalink

ok... great I should have tried just a little bit more before posting. After I turned off the exception breakpoints in the debugger properties, debugging seems to be working.

It seems that the debugger because of this setting stopped every time it didn't find a class (which is happening quite often in the starting process ;-).

Christian

0
Comment actions Permalink

You're my hero :)

0

Please sign in to leave a comment.