Bug 181661 - Timing hole in the JavaScript debugger can cause next debug session not to work.
Summary: Timing hole in the JavaScript debugger can cause next debug session not to work.
Status: ASSIGNED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: ATF (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-09 16:45 EDT by Robert Goodman CLA
Modified: 2020-05-07 10:51 EDT (History)
1 user (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 Robert Goodman CLA 2007-04-09 16:45:33 EDT 
There is a timing hole in the JavaScript debugger which will sometimes causes the second debug session not to work. The problem seems to occur when the debugger is sitting on a breakpoint and the terminate button is press. If the "onExecute()" method isn't doesn't wake up from the waitLoop() and run to completion before the JSDebugTarget method stopDebugger() calls debuggerService.off(), the next debug session doesn't stop on any breakpoints.
Comment 1 Philippe Ombredanne CLA 2008-03-03 14:43:02 EST 
See Bug 178825
Comment 2 Philippe Ombredanne CLA 2008-03-03 15:33:39 EST 
Assigning to me. Will commit the patches from bug 178825 in a new branch.