[TIMOB-6538] Android: Debugger: V8: Implement Ti.API.debugBreak for JS suspend
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-12-15T15:23:46.000+0000 |
| Affected Version/s | Release 1.8.0.1 |
| Fix Version/s | Sprint 2011-50, Release 1.8.0.1, Release 2.0.0 |
| Components | Android |
| Labels | branch-v8 |
| Reporter | Wilson Luu |
| Assignee | Josh Roesslein |
| Created | 2011-12-09T11:44:40.000+0000 |
| Updated | 2011-12-15T15:23:46.000+0000 |
Description
Our V8 adapter currently sends a "suspend" message for the Suspend action from TiStudio, but this suspends the thread regardless of the current state. We need to use the "DebugBreak" API in V8 to correctly suspend on the next entrance into Javascript.
This can be tested w/ Test Case 1023 in the [Debugger Test Plan](http://wiki.appcelerator.org/display/tp/Debugger+Test+Plan)
Looks like a "continue" request is being sent by Studio shortly after it sent a "suspend" request: https://gist.github.com/2bd748c1a9efc0ddf3a5 Will need input from Max on this behavior and if it is the source of the bug.
Tested this with Ti Mob SDK version 1.8.0.1.v20111214093905 and after running the example steps, when one hits step 4: Click 'Callframe nesting' button the debugger stops at break point 91 and not 90 like expected
This may just be a behavioral difference in V8 we cannot change.