Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-8644] Android: V8 Debugger's naming conventions for displayed Frame and Thread titles are not consistent.

GitHub Issuen/a
TypeBug
PriorityLow
StatusClosed
ResolutionWon't Do
Resolution Date2020-01-10T18:04:19.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsAndroid
Labelscore, qe-and040912
ReporterRobert Collazo
AssigneeUnknown
Created2012-04-10T01:49:19.000+0000
Updated2020-01-10T18:04:19.000+0000

Description

Based on results recorded in Debugger Test Plan and results logged from iOS tests, the Thread and Frame title naming conventions used for V8 debugging is not consistent. Steps to reproduce: 1. Create a new Titanium mobile project 2. Add/overwrite the newly created files in the Resources folder, with attached: app.js, import.js, nextwin.js (Zippped) 3. Copy attached *.bkpt files to the new project's Resources folder 4. Reference the Studio Debugger Test Plan (wiki.appcelerator.org/display/tp/Debugger+Test+Plan), and observe the following: Test Case: 1013 - SUSPEND TEST Step: 9 Expected: --------- In Debug view, confirm 2 call frames:  [Eval script] [app.js:9]  [Top-level script] [app.js:40]  Actual: ------- f() [app.js:9] Ti.UI.createButton.title() [app.js:40] Test Case: 1013 - SUSPEND TEST Step: 23 Expected: --------- In Debug view, confirm 3 call frames: cfb() [app.js:74] cfa() [app.js:79] [Top-level script] [app.js:91] Actual: ------- cfb() [app.js:74] cfa() [app.js:79] Ti.UI.createButton.title() [app.js:91] * Also note Attached log and capture files

Attachments

FileDateSize
LogFiles.zip2012-04-10T01:49:19.000+0000471983
TestFiles.zip2012-04-10T01:49:19.000+00005130

Comments

  1. Alan Hutton 2020-01-10

    This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.

JSON Source