[TIMOB-11182] Android: Debugger: breakpoints at line 1 skipped and resumed at next statement
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | Release 2.1.2, Release 3.0.0 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | debugger, parity, qe-and090112 |
| Reporter | Dustin Hyde |
| Assignee | Unknown |
| Created | 2012-09-26T23:28:46.000+0000 |
| Updated | 2018-02-28T20:04:19.000+0000 |
Description
Breakpoints at line 1 are not hit by debugger, but next statement is instead.
This is not a regression. This does not occur in iOS.
Steps to Reproduce:
1. Debug with code (manually enter breakpoint as per comment):
var x = 0; // breakpoint
function y(z){
return z + 1;
}
var q = y(1);
alert('q == ' + q);
Actual Result:
Line 7 is hit by debugger instead of line 1.
Expected Result:
Line 1 should be hit by debugger. The workaround is to move all code down one line, so the code begins at line 2, and the breakpoint is at line 2.
Attachments
| File | Date | Size |
|---|---|---|
| androiddebugger.log | 2012-09-26T23:28:46.000+0000 | 2693 |
| iosdebugger.log | 2012-09-26T23:28:46.000+0000 | 2061 |
This issue is seen on android & not on IOS with the current GA stack. Environment: Appc Studio : 4.4.0.201511241829 Ti SDK : 5.1.1.GA Ti CLI : 5.0.5 Alloy : 1.7.26 MAC Yosemite : 10.10.5 Appc NPM : 4.2.2 Appc CLI : 5.1.0 Node: v0.12.27 Nexus 6 - Android 6.0