P
Peter Duniho
And as long as I'm asking questions...
I can't figure out how to get the Eclipse debugger to break into a thread
automatically if a null reference exception occurs.
I know that Eclipse generally should do this, because the Windows version
works as I expected it to by default. But on the Mac, I can watch a null
reference exception come up in the console window, but the application
just keeps chugging away happily. I never break into the debugger as I
expected to.
The only setting I found that seems to relate to this is in the Java/Debug
preferences, and I do have it set ("Suspend execution on uncaught
exceptions"). I suppose by implication this may mean that the exception
was actually caught and handled somewhere. But where? How do I stop them
from being handled (if that is indeed the problem)? And why does it work
differently on the Mac than on Windows? Does this mean it's the JRE
that's actually getting in the way somehow?
Thanks!
Pete
(...and yes, I realize there are Eclipse newsgroups...I searched them and
found nothing on this particular topic, though queries that involve "null
reference exception" turn up lots of other stuff. I posted here because,
well...I don't need another username and password to do so and it seems
reasonably on-topic to me. I figure there's a good chance that at least
some of the folks here are using Eclipse and have some experience with
something like this ).
I can't figure out how to get the Eclipse debugger to break into a thread
automatically if a null reference exception occurs.
I know that Eclipse generally should do this, because the Windows version
works as I expected it to by default. But on the Mac, I can watch a null
reference exception come up in the console window, but the application
just keeps chugging away happily. I never break into the debugger as I
expected to.
The only setting I found that seems to relate to this is in the Java/Debug
preferences, and I do have it set ("Suspend execution on uncaught
exceptions"). I suppose by implication this may mean that the exception
was actually caught and handled somewhere. But where? How do I stop them
from being handled (if that is indeed the problem)? And why does it work
differently on the Mac than on Windows? Does this mean it's the JRE
that's actually getting in the way somehow?
Thanks!
Pete
(...and yes, I realize there are Eclipse newsgroups...I searched them and
found nothing on this particular topic, though queries that involve "null
reference exception" turn up lots of other stuff. I posted here because,
well...I don't need another username and password to do so and it seems
reasonably on-topic to me. I figure there's a good chance that at least
some of the folks here are using Eclipse and have some experience with
something like this ).