Eclipse Community Forums: Java Development Tools (JDT) » Debugger stops at a breakpoint but has "lost its way"

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Debugger stops at a breakpoint but has "lost its way"

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

Debugger stops at a breakpoint but has "lost its way" [message #242983]

Thu, 19 April 2007 19:48

Ivan Biddles

Messages: 22
Registered: July 2009

Junior Member

Hi,

Since installing 3.3M6 I am continually experiencing a problem with the
debugger.

At least 50% of the time, the debugger apparently stops at a breakpoint
but has "lost its way":

a. The variables view is blank
b. The F5/6/7/8 keys do not respond
c. The debug view controls are greyed out
d. The list of threads in the debug view is collapsed (the
current thread is not expanded and the breakpoint not highlighted)
e. The debug view sometimes minimizes itself to a fast view

This did not happen previous to 3.3M6 that I noticed but it has become a
major annoyance. It often happens even as you are just stepping from line
to line -- suddenly the variables window goes blank, etc.

The (highly unsatisfactory) workaround is to go back to the debug view,
re-expand the thread you are interested in and double-click (a single
click doesn't do it) on the latest breakpoint. Sometimes that doesn't even
work and you have to keep selecting and deselecting entries in the thread
stack until it eventually rights itself.

The specific debugging scenario I have right now is that I am running
another version of Eclipse in the debugger while developing a plug-in.

I looked in bugzilla but couldn't find a bug that appears from the
description to be exactly like this so I thought I'd post to the forum
before raising a new bug.

Has anyone seen this or is it a known issue?

Best wishes, Ivan.

Report message to a moderator

Re: Debugger stops at a breakpoint but has "lost its way" [message #242984 is a reply to message #242983]

Thu, 19 April 2007 20:48

Eclipse User

Originally posted by: wharley.bea.com

"Ivan Biddles" <ivanb@scientology.net> wrote in message
news:0643bc50664028e7be97606030b49ddf$1@www.eclipse.org...
> Hi,
>
> Since installing 3.3M6 I am continually experiencing a problem with the
> debugger.
> At least 50% of the time, the debugger apparently stops at a breakpoint
> but has "lost its way":

Yes, it's a known issue (in fact I think I posted the bug number here a
couple days ago, or maybe it was on eclipse.platform).

It's fixed in recent builds. Pick up the latest I-build.

Report message to a moderator

Re: Debugger stops at a breakpoint but has "lost its way" [message #244092 is a reply to message #242984]

Tue, 29 May 2007 15:42

Curtis Windatt

Messages: 166
Registered: July 2009

Senior Member

This problem has shown up for several reasons and has been "fixed" several
times. The most recent issue was just fixed for RC2. If anyone sees this
problem using the latest integration build, please file a bug against JDT
Debug asap so we can look at it for 3.3.

Curtis

"Walter Harley" <wharley@bea.com> wrote in message
news:f08kil$jno$1@build.eclipse.org...
> "Ivan Biddles" <ivanb@scientology.net> wrote in message
> news:0643bc50664028e7be97606030b49ddf$1@www.eclipse.org...
>> Hi,
>>
>> Since installing 3.3M6 I am continually experiencing a problem with the
>> debugger.
>> At least 50% of the time, the debugger apparently stops at a breakpoint
>> but has "lost its way":
>
> Yes, it's a known issue (in fact I think I posted the bug number here a
> couple days ago, or maybe it was on eclipse.platform).
>
> It's fixed in recent builds. Pick up the latest I-build.
>

Report message to a moderator

Previous Topic:	How do I find/read/write plug-in resources?
Next Topic:	debug: conditional watchpoint?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Nov 12 19:48:17 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter