Bug 405654 - DBGp 'break' and 'stack_get' commands can occur out of order
Summary: DBGp 'break' and 'stack_get' commands can occur out of order
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common-Debug (show other bugs)
Version: 4.0   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-12 17:25 EDT by Adam Hawthorne CLA
Modified: 2013-04-17 12:27 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 Adam Hawthorne CLA 2013-04-12 17:25:31 EDT 
We are implementing a debugger for our language using DLTK/DBGp .  When I press the 'suspend' button in the Debug UI (which corresponds to a DBGp 'break' command), the UI simultaneously sends a 'stack_get' command.  My debugger engine sometimes receives the stack_get before the break, and sometimes afterwards.  It seems that there is an unintentional thread race between the UI issuing the 'stack_get' and the DLTK core issuing the 'break'.

Unfortunately this means we have to rearchitect our code to support 'synchronous' calls during an 'asynchronous' point in time, and some of the other constraints of the protocol become less clear.