1. 23 Sep, 2011 1 commit
  2. 19 Sep, 2011 1 commit
  3. 29 Aug, 2011 1 commit
  4. 08 Aug, 2011 1 commit
  5. 05 Aug, 2011 1 commit
  6. 07 Jul, 2011 2 commits
  7. 06 Jul, 2011 1 commit
  8. 30 Jun, 2011 1 commit
  9. 29 Jun, 2011 1 commit
    • sgjesse@chromium.org's avatar
      Support debugger inspection of locals in optimized frames · 7d2be7c0
      sgjesse@chromium.org authored
      Optimized frames are now handled by the debugger. When discovering optimized frames during stack inspection in the debugger they are "deoptimized" using the normal deoptimization code and the deoptimizer output information is used to provide frame information to the debugger.
      
      Before this change the debugger reported each optimized frame as one frame no matter the number of inlined functuions that might have been called inside of it. Also all locals where reported as undefined. Locals can still be reposted as undefined when their value is not "known" by the optimized frame.
      
      As the structures used to calculate the output frames when deoptimizing are not GC safe the information for the debugger is copied to another structure (DeoptimizedFrameInfo) which is registered with the global deoptimizer data and processed during GC.
      
      R=fschneider@chromium.org
      
      BUG=v8:1140
      TEST=test/mjsunit/debug-evaluate-locals-optimized*
      
      Review URL: http://codereview.chromium.org//7230045
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8464 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7d2be7c0
  10. 16 Jun, 2011 1 commit
  11. 06 May, 2011 1 commit
  12. 06 Apr, 2011 1 commit
  13. 01 Apr, 2011 1 commit
  14. 30 Mar, 2011 1 commit
  15. 25 Mar, 2011 2 commits
  16. 18 Mar, 2011 3 commits
  17. 02 Feb, 2011 2 commits
  18. 01 Feb, 2011 1 commit
  19. 24 Jan, 2011 1 commit
  20. 22 Dec, 2010 1 commit
  21. 20 Dec, 2010 1 commit
  22. 07 Dec, 2010 4 commits