Bugzilla – Full Text Bug Listing
| Summary: | [breakpoints] Compilation error in breakpoint can't be corrected | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ulrich Hobelmann <ulrich.hobelmann> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | darin.eclipse, Michael_Rennie, ori.kremer |
| Version: | 3.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Ulrich Hobelmann
The same problem sometimes occurs in the expressions and display views: the expressions entry will stay red and not display a value, and the display view will print "Evaluation failed. Reason(s): Evaluations must contain either an expression or a block of well-formed statements" on "display". The expression I'm trying to evaluate is usually something like object.getSomething(), and yes, I'm positive there are no trailing or missing parentheses around/in the expression. Interestingly, the variables view will display the contents of 'object' and even a correct popup with instance fields of 'object' is shown in the Java editor when I hover above it. This problems seems to occur whenever the system is remotely debugged (i.e. when I connect Eclipse to my running JBoss server). JDK is 1.6.0_11 in both cases, but the server uses the server VM. JBoss is 4.2.2GA. The deployed server code was built with Sun's javac in Java5-mode. Both Expressions and conditional breakpoints do not work, the complaint being that the expression is not valid. If I use non-conditional breakpoints, however, I can see the variable used in the stack frame. Trying to evaluate an expression (or just the variable name) in the Display view also fails. Could there be a mismatch between workspace compiler settings and what the server VM can handle? I don't believe so. The build target for 'javac' should be set to Java 5, and the server VM is 1.6.0_11 (jdk) anyway (just using server, not client VM). Is there a difference in the code that's used for the Variables view and that's used to access variables that are used in expressions/conditions/...? That's the only reason I can think of that could explain why Variables can be looked at, but everything that involves evaluation does not. For the record, server debugging works for me with Eclipse 3.5M4 (great and awesomely stable, btw!). It may also have to do with upgrading JBoss from 4.2.2 to 4.2.3 (which we also just did), but I don't think that should make a difference, as it's rather unrelated to debugging tech. Correction: sometimes it works with 3.5M4, sometimes not. Right now it works in the second stackframe (ctrl-shift-I for inspect shows a variable's value there), but in the top stackframe (method with two nested for-loops and a switch inside them) it doesn't, and conditional breakpoints fail there, too. Note bug 277187 was fixed in 3.5RC2. Can someone re-test to see if this problem is also fixed? (In reply to comment #7) > Note bug 277187 was fixed in 3.5RC2. Can someone re-test to see if this problem > is also fixed? > I'm experiencing the same error in 3.5 GA when remote debugging (a JBoss web app). This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |