Bug 26420 - Debugger jumps to top of file while debugging
Summary: Debugger jumps to top of file while debugging
Status: RESOLVED DUPLICATE of bug 26098
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-14 16:49 EST by John Arthorne CLA
Modified: 2002-11-15 10:33 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2002-11-14 16:49:16 EST
Build 20021114

Sometimes while stepping (F6), the debugger will jump to the first line of the
file, and a little blue arrow will appear in the marker bar.  I've never seen
this arrow before so I don't know what it signifies.  Hitting F6 again will jump
back to the correct place in the original method.  Others have seen this too,
but we haven't been able to construct a simple test case.

A not so simple test case is in:

Project: org.eclipse.core.tests.resources (in dev.eclipse.org/home/eclipse)
Class: org.eclipse.core.tests.resources.LinkedResourceTest
Breakpoint at the start of testAllowMissingLocal

After the breakpoint is hit, step into the "createLink" method, then repeatedly
hit F6 to step over.  About every third step it will jump to the top of the file
and show that little blue arrow.
Comment 1 Darin Wright CLA 2002-11-14 17:58:10 EST
JCORE admitted to causing some debug attribute trouble - this may still be the 
case.

The blue arrow is the new "instruction pointer". You should see it in the ruler 
as you step, corresponding to the current execution location.
Comment 2 Darin Wright CLA 2002-11-14 21:20:35 EST
Looks like another case of bug 26098
Comment 3 Darin Wright CLA 2002-11-14 21:40:55 EST
I debugged the test with no problem. I also checked the debug attributes of the 
file and found the line number to be 0 (not -1) as bug 26098 states. It is 
possible that you need to rebuild your entire workspace (perhaps the class file 
is old due to incremental building). Please try a full build and see if this is 
still a problem.
Comment 4 John Arthorne CLA 2002-11-15 10:33:53 EST
I did a full rebuild with the 20021113 build and it didn't fix the problem.  I
then grabbed the 20021114 build, and after a full rebuild the problem went away.
So this appears to indeed be a duplicate of bug 26098.

*** This bug has been marked as a duplicate of 26098 ***