[TIMOB-3767] Android: Debugger breakpoint conditions with failures should report an error in the debugger console, but still break
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Won't Fix |
Resolution Date | 2017-07-31T20:52:08.000+0000 |
Affected Version/s | Release 1.7.0 |
Fix Version/s | n/a |
Components | Android |
Labels | merge-1.8.1, parity |
Reporter | Marshall Culpepper |
Assignee | Eric Merriman |
Created | 2011-04-27T13:14:13.000+0000 |
Updated | 2017-07-31T20:52:33.000+0000 |
Steps to test: - Right click on an enabled breakpoint in a debugged app, go to Properties - Enable the Breakpoint Condition, enter an invalid expression - The next time that code runs, a failure should show in the Console, but the breakpoint should still break
Using
with the breakpoint set on the
Ti.API.debug
statement and the conditional set toi ==
. I get the following crash.This was stuck in TBS. Moved to sprint 25.
This appears to have already been fixed. I've re-tested Don's test case and the breakpoint error is correctly reported to the app's console in TiStudio, while the breakpoint itself seems to work fine.
Tested with 1.8.0.v20110909152148 on Win 7 Linux 10.04 Mac OS X 10.6.8 ported test to Debugger test plan
Standardizing summary and labels.
moving sprint so it can be verified and closed if need be. was this resolved with 1.8.0?
TiApp crashes on build 1.8.0.1 running Rhino on Windows 7 and XP:
I do not get the NullPointerException when compared to Don's crash. But, when running the same for loop code on V8 (1.8.0.1, Windows 7 and XP), TiApp does not crash. It loops through and prints out the count.
Tested with 1.8.0.1 on Mac 10.6.8, Linux 10.04 and Window 7 and XP. Rhino is working as expected, but V8 does not stop at the breakpoint, may be related to TIMOB-4162, leaving open until we can confirm that it is working on V8
Closing due to inactivity. If this issue still exists, please raise a new ticket.