You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Currently, breakpoints that are conditional are always triggered as if there were no condition on them. It would be nice to support them. Even better would be if this could be done by writing Java, so you can have something of the form:
If this is too hard for now, then perhaps it should be documented in the "Status" section of the project's home page that the conditions on conditional breakpoints are ignored (which is what I assume is happening).
The text was updated successfully, but these errors were encountered:
Point taken - conditional breakpoints breaking "unconditionally" deserves mentioning on the status page.
The beauty of how SDBG is integrated with the Eclipse Java Development Tools is that SDBG is reusing the breakpoints (including the conditional ones) which are actually placed and owned by the standard Java (JDWP) debugger. So if you have shared code between the client and server, you don't have to think whether you need an SDBG breakpoint, or a Java breakpoint.
I had in mind exactly the cheat you described. I think it is better to have some possibility of conditional breakpoints than have non. I work on a large GWT application and it is frustrating to jump from eclipse to chrome dev tools.