1

I have a handler on the "Low Memory Detector" thread, and although Eclipse lets me set breakpoints in the code in my handler, it runs through the breakpoint-tagged lines without pausing the thread. (Breakpoints in other threads are working normally.) Is this expected behavior? Is there a trick to aid debugging in this situation?

(This thread is for notifications from the MXMemoryBean.)

Joshua Goldberg
  • 5,059
  • 2
  • 34
  • 39
  • I'm running Eclipse Helios (3.6), in case that makes a difference. – Joshua Goldberg Feb 05 '13 at 14:40
  • What's your JDK version? It might be related to a bug in [JDK6u 14](http://stackoverflow.com/questions/1370868/eclipse-debugger-doesnt-stop-at-breakpoint). – ericson Feb 05 '13 at 15:49
  • That linked question sounds just like my problem, but I think I may be upgraded past the fix ---- java version "1.6.0_39" / Java(TM) SE Runtime Environment (build 1.6.0_39-b04-442-10M4008) / Java HotSpot(TM) 64-Bit Server VM (build 20.14-b01-442, mixed mode) – Joshua Goldberg Feb 05 '13 at 16:19
  • Trying -XX:+UseParallelGC did not help the problem. (This appears to be one of the bug reports for the issue referenced above: http://bugs.sun.com/view_bug.do?bug_id=6862295 ) – Joshua Goldberg Feb 05 '13 at 17:26

0 Answers0