Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311624 - [examples] PDA examples do not terminate cleanly
Summary: [examples] PDA examples do not terminate cleanly
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 16:21 EDT by Michael Rennie CLA
Modified: 2019-11-14 03:30 EST (History)
2 users (show)

See Also:


Attachments
screenshot (100.53 KB, image/png)
2010-05-04 16:21 EDT, Michael Rennie CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2010-05-04 16:21:15 EDT
Created attachment 167037 [details]
screenshot

I20100504-0800

trying to test the patch for bug 311207 I found that the PDA debug target would not terminate cleanly - such that the suspend button would stay enabled and the instruction pointer would not go away.

See attached screen shot.

I tried resetting the view management settings, resetting the debug perspective and closing / reopening the debug perspective to no avail.
Comment 1 Hernan Gonzalez CLA 2011-11-03 10:12:25 EDT
In case someone finds this useful:

I was experienced this problem with my own DebugTarget (based http://www.eclipse.org/articles/Article-Debugger/how-to.html ) , the resume button stayed active after termination.

I fixed by changing  hasThreads() method:


public boolean hasThreads() throws DebugException {
	return fTerminated ? false : true; 
}
Comment 2 Lars Vogel CLA 2019-11-14 03:30:12 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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.