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

Bug 389900

Summary:	Debugger loses selection during debugging (was: breakpoints dont allow stepping)
Product:	[Eclipse Project] JDT	Reporter:	Eric Fitting <efitting>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.duft, Michael_Rennie
Version:	4.2
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:	stalebug

Description Eric Fitting

2012-09-19 10:24:38 EDT

while debugging a multithreaded java application, the first time a [suspend_vm] breakpoint triggers I am unable to step through the program. If I press resume and another breakpoint is hit (or the same breakpoint is hit again) I am able to step normally.

Comment 1 Michael Rennie

2013-01-10 11:26:11 EST

Can you provide a snippet and more exact steps? Running a simple threaded app that suspends the VM works fine for me using:

Version: 4.3.0
Build id: I20121218-1600

Comment 2 Eric Fitting

2013-01-10 11:52:35 EST

I see the issue fairly extensively while debugging, but it does not happen all the time. It is limited to suspend VM breakpoints, and has something to do with thread selection in the debug view. I found that if I manually look through the debug view and find the thread that is suspended at the breakpoint and select it, I am able to use the debugger normally. Sometimes the debugger automatically selects the thread that was suspended (as expected) but when it fails, there is no thread selected. The application I am running has 50+ threads.

Comment 3 Michael Rennie

2013-09-16 12:06:37 EDT

Do you have thread groups turned on? In which case it would be a dupe of bug 126379. Otherwise likely a dupe of bug 252515.

Comment 4 Markus Duft

2014-05-14 05:20:26 EDT

We see the same issue when debugging applications with many threads on Linux. And we see it so frequent that people are quite annoyed. Actually there is nearly no debugging session that does not hit the problem. Especially with many threads this is extremely uncool as it takes a while to find the thread again ;)

We don't have threadgroups, and i could not see any association to the Variables view or something like that. It seems a problem local to the "Debug" view.

Comment 5 Eclipse Genie

2020-01-23 14:13:08 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.