Eclipse Community Forums: Java Development Tools (JDT) » Conditional breakpoints in remotely debugged process

Home » Language IDEs » Java Development Tools (JDT) » Conditional breakpoints in remotely debugged process(Helios, Snow Leopard, JVM 1.6.0_17, bad behavior)

Show: Today's Messages :: Show Polls :: Message Navigator

Conditional breakpoints in remotely debugged process [message #640425]

Mon, 22 November 2010 02:04

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.

Report message to a moderator

Re: Conditional breakpoints in remotely debugged process [message #640475 is a reply to message #640425]

Mon, 22 November 2010 08:40

Mauro Molinari

Messages: 285
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.

Report message to a moderator

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:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 13:36:05 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter