1. 07 Mar, 2012 1 commit
  2. 28 Feb, 2012 1 commit
  3. 16 Jan, 2012 1 commit
  4. 06 Oct, 2011 1 commit
  5. 19 Sep, 2011 1 commit
  6. 13 Sep, 2011 1 commit
  7. 16 May, 2011 1 commit
  8. 06 May, 2011 2 commits
  9. 05 May, 2011 1 commit
  10. 04 May, 2011 3 commits
  11. 18 Mar, 2011 3 commits
  12. 11 Feb, 2011 1 commit
  13. 07 Dec, 2010 3 commits
  14. 17 Nov, 2010 1 commit
  15. 12 Nov, 2010 1 commit
  16. 25 Oct, 2010 1 commit
  17. 05 Oct, 2010 1 commit
  18. 17 Jun, 2010 1 commit
  19. 14 Apr, 2010 1 commit
  20. 15 Jan, 2010 1 commit
  21. 05 Nov, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Fix issue 493: Infinite loop when debug break is set when entering function.apply. · 41d6cae4
      sgjesse@chromium.org authored
      In the generated code for function.apply there was a loop checking the stack limit for interruption. This loop would call into the runtime system to handle interuption and keep running until there was no interruption. However if the interuption was debug break the runtime system would never clear the interruption as debug break is prevented in builtins are prevented and the assumption here was that returning with the debug break flag set would move execution forward.
      
      Renamed initial_jslimit and initial_climit to real_jslimit and real_climit. Renamed a few external references related to the stack limit as well.
      
      Exposed the real stack limit to generated code to make the stack check when entering function.apply use the real stack limit and not the stack limit which is changed to signal interruption.
      
      Added the real stack limit to the roots array.
      
      BUG=http://code.google.com/p/v8/issues/detail?id=493
      TEST=cctest/test-debug/DebugBreakFunctionApply
      Review URL: http://codereview.chromium.org/345048
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3229 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      41d6cae4
  22. 13 Oct, 2009 1 commit
  23. 01 Oct, 2009 1 commit
  24. 28 Sep, 2009 1 commit
  25. 26 Aug, 2009 1 commit
  26. 19 Aug, 2009 2 commits
  27. 04 Aug, 2009 1 commit
  28. 25 May, 2009 1 commit
  29. 20 May, 2009 1 commit
  30. 20 Apr, 2009 1 commit
  31. 13 Mar, 2009 1 commit
    • sgjesse@chromium.org's avatar
      A new stack guard break flag DEBUGCOMMAND has been introduced. This is used to... · 17b498c9
      sgjesse@chromium.org authored
      A new stack guard break flag DEBUGCOMMAND has been introduced. This is used to signal debug break due to debugger commands available in the queue for processing. If a stack guard break happens with this flag and not the DEBUGBREAK flag the no debug break event is generated and execution is resumed automatically when all debugger commands in the queue has been processed.
      
      This makes it possible to remote debuggers to just add commands to the queue without having to request a break as well. As soon as any JavaScript executes the debugger commands will be processed and the response send to the remote debugger.
      
      Currently hide this behind a flag (--debugger-auto-break) as the current command line debugger in Chrome is not designed for this new behaviour, whereas the new Chrome developer tools will use it.
      Review URL: http://codereview.chromium.org/42173
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1508 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      17b498c9
  32. 26 Jan, 2009 1 commit