[TIMOB-9808] Android: Debugger: V8 - The variables view does not show all variables for a given javascript file
| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | Medium |
|---|
| Status | Closed |
|---|
| Resolution | Won't Fix |
|---|
| Resolution Date | 2012-11-16T21:15:08.000+0000 |
|---|
| Affected Version/s | Release 2.1.0 |
|---|
| Fix Version/s | 2012 Sprint 23 Core, 2012 Sprint 23 |
|---|
| Components | Android |
|---|
| Labels | core, qe-stud060412 |
|---|
| Reporter | Michael Pettiford |
|---|
| Assignee | Max Stepanov |
|---|
| Created | 2012-06-26T16:10:01.000+0000 |
|---|
| Updated | 2013-03-27T22:32:22.000+0000 |
|---|
Description
*Note this is not a regression, it occurs in Ti Studio 2.0.2 and Ti Mobile SDK 2.0.2GA*
Steps to reproduce:
1. Import the attached app into Ti Studio (Remove the breakpoints directory from the app)
2. Add the attached breakpoint file (breakpoint-args.bkpt) in the debug breakpoint view
3. Run the app in debug mode
4. Press the open window button
5. Press the Arguments button
6. Open the variables view
Actual result:
The variable encode from nextwin.js is not listed in the variables view
*Note this variable is listed when running it on iOS*
Expected result:
The variable encode is listed along with the other variables from nextwin.js
Attachments
Michael--I believe this is not a Studio but rather a SDK issue. Can you please chat with Max about it?
Correct, Studio displays all the information received through debugger connection. JS engines can report variables differently, e.f V8 has everything native compiled.
The way JS variable are initialized and used internally by V8 is out of out control since it's being optimized in native.