1. 16 May, 2011 1 commit
  2. 23 Mar, 2011 1 commit
  3. 01 Feb, 2011 1 commit
  4. 28 Jan, 2011 1 commit
  5. 22 Dec, 2010 1 commit
  6. 14 Dec, 2010 1 commit
  7. 15 Oct, 2010 1 commit
  8. 10 Jun, 2010 1 commit
  9. 01 Apr, 2010 1 commit
  10. 30 Mar, 2010 1 commit
  11. 23 Mar, 2010 1 commit
  12. 19 Feb, 2010 1 commit
  13. 12 Feb, 2010 1 commit
  14. 01 Feb, 2010 1 commit
  15. 15 Jan, 2010 1 commit
  16. 01 Dec, 2009 1 commit
  17. 30 Oct, 2009 1 commit
  18. 13 Oct, 2009 1 commit
  19. 23 Sep, 2009 1 commit
  20. 08 Sep, 2009 1 commit
  21. 29 Jun, 2009 1 commit
  22. 23 Jun, 2009 1 commit
  23. 22 Jun, 2009 1 commit
  24. 18 Jun, 2009 1 commit
  25. 12 Jun, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Add scope chain information to the debugger. · 88261439
      sgjesse@chromium.org authored
      For each frame it is now possible to request information on the scope chain. Each scope in the chain can have one of the types local, global, with and closure. For scopes of type global and with the mirror for the actual global or with object is available. For scopes of type local and closure a plain JavaScript object with the materialized content of the scope is created and its mirror is returned. Depending on the level of possible optimization the content of the materialized local and closure scopes might only contain the names which are actually used.
      
      To iterate the scope chain an iterator ScopeIterator have been added which can provide the type of each scope for each part of the chain. This iterator creates an artificial local scope whenever that is present as the context chain does not include the local scope.
      
      To avoid caching the mirror objects for the materialized the local and closure scopes transient mirrors have been added. They have negative handles and cannot be retrieved by subsequent lookup calls. Their content is part of a single response.
      
      For debugging purposes an additional runtime function DebugPrintScopes is been added.
      
      Added commands 'scopes' and 'scope' to the developer shell and fixed the dir command.
      
      BUG=none
      TEST=test/mjsunit/debug-scopes.js
      Review URL: http://codereview.chromium.org/123021
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2149 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      88261439
  26. 08 Jun, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Add more debugging information to scripts compiled through eval. · d498361c
      sgjesse@chromium.org authored
      Scripts now have a compilation type which can be host, eval or JSON. Host scripts are compiled through the API, eval scripts are compiled through call to evan and JSON scripts are compiled as a result of calling JSON.parse.
      
      For scripts scripts compiled through eval the JavaScript function in top of the stack and the pc offset into the code is stored in the script object. This makes it possible to calculate the source position of the eval call later when requested. This information can be obtained through the script mirror object and is part of the script mirror JSON serialization for the debugger protocol.
      
      Moved the enumeration ScripType into class Script and remamed to Type. The new compilation type enumeration is also inside the class Script.
      
      This information is now shown when using the scripts command in he developer shell debugger.
      Review URL: http://codereview.chromium.org/119108
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2119 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      d498361c
  27. 15 May, 2009 2 commits
  28. 06 May, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Added context information to scripts. · b32d7d2e
      sgjesse@chromium.org authored
      Added a simple initial version of a context mirror object which just holds the user data from the context, and does not preserve handle identity.
      
      A script object now holds a reference to the custom data from the context it was compiled in. This data is included in the debugger protocol for scripts.
      
      Changed the serialization for the scripts command to use the mirror objects instaed of custom serialization. This included passing options from the debugger request to the serializer for including the full source of scripts in the response.
      Review URL: http://codereview.chromium.org/111001
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1877 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      b32d7d2e
  29. 05 May, 2009 1 commit
  30. 21 Apr, 2009 1 commit
  31. 15 Apr, 2009 1 commit
  32. 12 Mar, 2009 1 commit
  33. 10 Mar, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Whenever a script object is created it is assigned a unique id. Currently this... · 9d17b0d4
      sgjesse@chromium.org authored
      Whenever a script object is created it is assigned a unique id. Currently this id is assigned from an 32 bit integer counter.
      
      Changed the script break points to be able to handle both break points based on script names and script ids. When break points are set through a script id the position is relative to the script itself. This is different from the script break points set through script names where the line/coulmn offset is taken into account.
      
      This has the side effect that function break points are not converted into script break points for named scripts.
      
      Show the script id in the D8 shell debugger when listing all scripts using the 'scripts' command.
      Review URL: http://codereview.chromium.org/40317
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1468 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      9d17b0d4
  34. 05 Feb, 2009 2 commits
  35. 28 Jan, 2009 1 commit
  36. 26 Jan, 2009 1 commit
  37. 22 Jan, 2009 1 commit
  38. 21 Jan, 2009 1 commit