Bugzilla – Full Text Bug Listing
| Summary: | Abort a pending step if no StepEvent is received prior to a SuspendEvent | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Michael Rennie <Michael_Rennie> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | hernanpepe, thatnitind | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.4 M3 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 367806 | ||||||
| Attachments: |
|
||||||
applied to HEAD |
Created attachment 204091 [details] proposed fix Depending on the implementation of the EventQueue / EventRequestManager it could be possible to process a SuspendEvent when no StepEvent has been received. For example: you step return from a function and the remote VM (browser) immediately suspends (on a breakpoint or exception) - in this case the thread that initiated the step would still think it was still stepping and be in the wrong state (waiting for a StepEvent that will never come).