Question About Eclipse Java Debugger Conditional Breakpoints Inefficiency
Posted
by Personman
on Stack Overflow
See other posts from Stack Overflow
or by Personman
Published on 2010-05-14T11:22:50Z
Indexed on
2010/05/14
11:24 UTC
Read the original article
Hit count: 183
I just set a conditional breakpoint in Eclipse's debugger with a mildly inefficient condition by breakpoint standards - checking whether a HashMap's value list (8 elements) contains Double.NaN. This resulted in an extremely noticeable slowdown in performance - after about five minutes, I gave up.
Then I copy pasted the condition into an if statement at the exact same line, put a noop in the if, and set a normal breakpoint there. That breakpoint was reached in the expected 20-30 seconds.
Is there something special that conditional breakpoints do that is different from this, or is Eclipse's implementation just kinda stupid? It seems like they could fairly easily just do exactly the same thing behind the scenes.
© Stack Overflow or respective owner