Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-6546] Android: Debugger - v8 - Args test case contains many unexpected variables

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2011-12-14T16:38:47.000+0000
Affected Version/sRelease 1.8.0.1
Fix Version/sSprint 2011-49, Release 1.8.0.1, Release 2.0.0
ComponentsAndroid
Labelsbranch-v8
ReporterEric Merriman
AssigneeMarshall Culpepper
Created2011-12-09T12:40:34.000+0000
Updated2014-06-19T12:44:10.000+0000

Description

While running the Args test, after step 6, many unexpected global and local variables appear in the variables pane. See attached image. Steps to reproduce: 1) Create a new project in studio called debug_test 2) Move the js files form the debug test project in titanium_mobile_tests_internal 3) refer to the test plan at http://wiki.appcelerator.org/display/tp/Debugger+Test+Plan 4) Execute test case 1021 Result: Many unexpected variables Expected: 'local' variables (a, b, c, i, arguments) 'global' variables (array, button, exception, encode, win, argtest, evt, x)

Attachments

FileDateSize
variable.jpg2011-12-09T12:40:34.000+0000235150

Comments

  1. Josh Roesslein 2011-12-11

    Should be fixed with variable filter fix.
  2. Michael Pettiford 2011-12-14

    When testing this with Ti Mob SDK build 1.8.0.1.v20111214093905 I noticed that after expanding arguments after step 7, there were extra variables included when there shouldn't have been any. Theses variables are: callee, length, _proto_ and constructor
  3. Natalie Huynh 2011-12-14

    Tested with 1.8.0.1.v20111214093905 on Win7, Lion. The extra arguments is not a bug, will open a new bug to track parity

JSON Source