Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 15949 - JDIDebugTarget can resume threads which hit a breakpoint early
Summary: JDIDebugTarget can resume threads which hit a breakpoint early
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-14 11:16 EDT by Jared Burns CLA
Modified: 2002-05-14 18:18 EDT (History)
0 users

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 Jared Burns CLA 2002-05-14 11:16:55 EDT 
When the JDIDebugTarget receives a ThreadStart event from the 
EventDispatcher, it votes "true" to resume the thread. This is a bug 
waiting to happen as there is no guarantee about when ThreadStart events 
are fired from the VM.

We can get ThreadStart notifications after a breakpoint has been hit, in 
which case we'd resume the user's thread for them. This could also make our 
model get out of synch as the thread could think it was suspended even 
though it was running.

When the JDIDebugTarget receives a ThreadStart event, it should vote 
"!thread.isSuspended()". This means that if it gets a ThreadStart for a 
thread that is suspended, it will keep the thread suspended.
Comment 1 Jared Burns CLA 2002-05-14 11:18:02 EDT 
Implemented. Please verify.
Comment 2 Jared Burns CLA 2002-05-14 11:18:24 EDT 
Marking fixed.
Comment 3 Darin Wright CLA 2002-05-14 18:18:30 EDT 
Verified.