| Summary: | CCE while debugging | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Deepak Azad <deepakazad> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael_Rennie |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Deepak Azad
Can you paste the snippet you were trying to evaluate? Now I cannot reproduce this with I20120207-2200. Did it get fixed last week? (In reply to comment #2) > Now I cannot reproduce this with I20120207-2200. Did it get fixed last week? No. still waiting on that snippet :) The thing is now I cannot reproduce the problem even with I20120131-2200.
In any case I will try to describe the problem as I remember, maybe you get a clue..
1. Create a 'Plug-in' project (not a Java project)
2. Create a type
package p;
class A {
void foo() {
String s = "abc";
}
}
3. Source > Externalize Strings (..and follow the steps in the wizard)
4. Breakpoint at
org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesFileEditor
Line 311 - return accessorType;
5. Open the Properties file created in step 3
=> the debugger will stop at the breakpoint
6. Step Over
=> Exception
I was essentially following these steps last week, but for some reason I do not see an exception today. Maybe something (else) went wrong in my previous debugger session?
Ha! can reproduce now even with I20120207-2200. 1. Breakpoint at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesFileEditor Line 308 - private IType findAccessorType(IProgressMonitor pm) ... 2. Add 'fIsStateValidationEnabled' as a watch expression. This is a private field in a supertype of PropertiesFileEditor, see org.eclipse.ui.texteditor.AbstractTextEditor.fIsStateValidationEnabled. 3. Open any properties file => Breakpoint from step 1 is reached => Exception => Expressions view shows the value of 'fIsStateValidationEnabled' as "(pending)" *** This bug has been marked as a duplicate of bug 282974 *** |