Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 438705

Summary:	Moving to next statement un-selects current thread
Product:	[Eclipse Project] JDT	Reporter:	Dudu Amar <duduamar>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	sarika.sinha
Version:	4.4
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Dudu Amar

2014-07-02 05:25:21 EDT

When I am debugging my JAVA application, moving to next statement (step into/step over) sometimes cases the selected thread (in the debug threads view) to be unselected, so i have to manually find it again in the thread list and click on it again. Otherwise I can't see current variables and I also can't go to next statement.

Comment 1 Sarika Sinha

2014-07-02 05:30:27 EDT

Can you provide a sample file and steps to reproduce this ?

Comment 2 Dudu Amar

2014-07-02 11:43:31 EDT

It is not consistent, but here is the sequence which it happens in:

1. Put a break point in line N in java application (heavily multi-threaded, maybe it happens only in such applications)
2. The code execution should reach this line and stop on it
2.1. Note that the current thread is selected in the threads list in the debug point
3. Click step into/step over
4. Execution moves to next line, but the current thread is no longer selected in the debug view. This causes variables not to be visible any more, and also clicking step over/into again has no effect, since the current (suspended thread) is no longer selected.

The workaround is to search for the suspended thread, and clicking/selecting it again.

Comment 3 Eclipse Genie

2020-03-02 11:46:44 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.