Community
Participate
Working Groups
Sometimes, the content assist doesn't work at all in the Display view: nothing happens when I press Ctrl+Space or select Content Assist in the context menu. When I change to another frame in the debug view, then it works in that other frame, but if I return to the frame where it didn't work, it still doesn't work. There is nothing logged in the Error Log view. May I enable logging or set a breakpoint to try to get more information about this bug? Eclipse SDK Version: 4.2.0 Build id: I20120608-1400
Can you reproduce it? How often does it happen? It would be great if you could try http://download.eclipse.org/eclipse/downloads/drops/R-3.8-201206081200/ and report back whether the problem happens there as well.
Created attachment 220829 [details] stacktrace Yes, I can reproduce it, in the sense that it happens every time I put a breakpoint in a specific method in my code and try to use the Display view. But I cannot reproduce it on a simple Java project. I ran the debugger under the debugger, and I got the attached stacktrace from JavaDebugContentAssistProcessor line 168. Note that setErrorMessage is called with the error status message, but the error message doesn't look to be displayed anywhere.
I tested with Eclipse 3.8 with the same plug-ins installed: completion works in the method where it didn't work on Eclipse 4.2.
The stacktrace looks like bug 215142, but it's strange that this should work on 3.8. Are you sure the breakpoints are on the same line, you have the same selection in the Debug view (and maybe the Variables view), and you try to complete on the same text in the Display view?
(In reply to comment #4) > The stacktrace looks like bug 215142, but it's strange that this should work > on 3.8. Are you sure the breakpoints are on the same line, you have the same > selection in the Debug view (and maybe the Variables view), and you try to > complete on the same text in the Display view? Yes, the breakpoints are on the same line. I have selected the top frame in the debug view, and selected nothing in the variables view. And in both cases I tried Ctrl+Space with no text in the Display view, and with the first characters of my variable name. I am using the same workspace and the same target platform with both Eclipse 3.8 and 4.2 But I have noticed a difference on Eclipse 4.2: when the debugger stops on the breakpoint, the tree node in the Debug view (corresponding to the thread in which it stops) appears open but with empty (or not drawn) nodes under it. Then when I click on the view, the node collapses, and I have to expand it again. No such weirdness happens on Eclipse 3.8
This was fixed in bug 400636 *** This bug has been marked as a duplicate of bug 400636 ***
