Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Conditional breakpoints in remotely debugged process(Helios, Snow Leopard, JVM 1.6.0_17, bad behavior)
Conditional breakpoints in remotely debugged process [message #640425] Sun, 21 November 2010 21:04 Go to next message
Jonathan Ross is currently offline Jonathan Ross
Messages: 1
Registered: November 2010
Junior Member
I have a situation where conditional breakpoints would save me a boatload of time, but am having trouble getting them to work.

In a local Java app, there's no issue.

When I debug a remote application, I get this error message every time: "Conditional breakpoint has compilation error(s). Reason: Evaluations must either contain an expression or a block of well-formed statements."

This happens no matter what the breakpoint condition is. I would have liked to use the "System.out.println(...something useful...); return false" idiom, but in fact true and false don't even work.

Eclipse and the app are running the same Java version on the same host: OS X 10.6, Eclipse 3.6, Java 1.6.0_17.

Any ideas greatly appreciated.
Re: Conditional breakpoints in remotely debugged process [message #640475 is a reply to message #640425] Mon, 22 November 2010 03:40 Go to previous message
Mauro Molinari is currently offline Mauro Molinari
Messages: 277
Registered: July 2009
Senior Member
Il 22/11/2010 03:05, Jonathan Ross ha scritto:
> When I debug a remote application, I get this error message every time:
> "Conditional breakpoint has compilation error(s). Reason: Evaluations
> must either contain an expression or a block of well-formed statements."

I encountered this same problem many times, although I couldn't say if I
was working with a local Java application or a remote one. I couldn't
reproduce in a consistent way, also because I feel like sometimes the
same conditional breakpoint works in a place and doesn't in another.

This drove me crazy in some situations :-(

If you are able to reproduce with a small test case, you may file a bug
against JDT/Debug. If you do, please post here the link, since I'm very
interested. Thank you!

Mauro.
Previous Topic:[SOLVED] How to apply a org.eclipse.ltk.core.refactoring.Change object to another project
Next Topic:Java 7 support in Eclipse 3.7
Goto Forum:
  


Current Time: Mon Jul 28 06:39:34 EDT 2014

Powered by FUDForum. Page generated in 0.01543 seconds