Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326073 - Debugger occasionally jumps back to beginning of some method
Summary: Debugger occasionally jumps back to beginning of some method
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 4.11 M1   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-23 11:46 EDT by MH CLA
Modified: 2019-03-29 04:46 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description MH CLA 2010-09-23 11:46:14 EDT 
Build Identifier: 20100617-1415

This happens every once in a while: when stepping through a method and even stop and just lock at the screen (without doing anything with keyboard/mouse), the debugger suddenly "jumps" to the beginning of the current or some other method in the call stack trace! The .log file doesn't show any entries when this happens.

This also occured occasionally with earlier Eclipse versions.

Reproducible: Sometimes
Comment 1 Eclipse Genie CLA 2018-12-26 19:15:49 EST 
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 2 Sarika Sinha CLA 2019-01-02 02:27:42 EST 
Please provide a reproducible scenario, if still able to reproduce.
Comment 3 M H CLA 2019-03-29 04:46:48 EDT 
This bug still occurs in the latest Eclipse versions and they are a major annoyance because you have to start debugging session all over again to have the desired data state.