Skip to content

V
V8
Switch branch/tag
  1. 28 Sep, 2009 1 commit
  3. 25 Sep, 2009 1 commit
  5. 09 Sep, 2009 2 commits
  7. 07 Sep, 2009 1 commit
  9. 19 Aug, 2009 1 commit
  11. 10 Jul, 2009 1 commit
  13. 09 Jul, 2009 1 commit
  15. 29 May, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Change the handling of the debug break stack guard. The debug break is no... · a019501b
      sgjesse@chromium.org authored 
      Change the handling of the debug break stack guard. The debug break is no longer ignored when hit inside "system" JavaScript. The reason for this is twofold:

* Running "system" JavaScript with the debug break flag active leads to slow running code while waiting for the break in non "system" JavaScript (one exception to this it is to try to avoid breaks in the clear mirror cache JavaScript code called when leaving the debugger).

* If this happens while processing RegExp running in native code an infinite loop is created as the stack guard handler for RegExp does not move execution forward

Fixed a GC bug in the interrupt handling for RegExp running in native code.

Added test of debug break while in debug message handler callback and debug break while executing a RegExp.
Review URL: http://codereview.chromium.org/115262

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2074 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a019501b
  17. 25 May, 2009 2 commits
  19. 18 May, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Add a script cache to the debugger · 94879a93
      sgjesse@chromium.org authored 
      When loaded scripts are requested this cache is filled with all the script objects in the heap. Hereafter its content is kept in sync with the active scripts in the heap through the notifications of new scripts compiled and by using weak handles to get notified when a script is collected.

Through the tracking of collected scripts the debugger event OnScriptCollected have been added to notify a debugger that a script previously returned through the scripts command is no longer in use.

Make the ComputeIntegerHash globally available.

Moved clearing of the mirror cache to when debugger is really left. Previously recursive invocations of the debugger cause the mirror cache to be cleared causing handles to become either stale or reference other objects.
Review URL: http://codereview.chromium.org/115462

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1988 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      94879a93
  21. 05 May, 2009 1 commit
  23. 04 May, 2009 1 commit
  25. 29 Apr, 2009 4 commits
  27. 24 Apr, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Removed the debug message thread. · 8fefc769
      sgjesse@chromium.org authored 
      The debug message thread was introduced to make it possible to have the message handler callback be called from a different thread than the thread running V8 where the debug event occoured, but it never had any practical use, and prevents providing information to the message handler which is only available from the V8 thread.

In the future any thread decoupling will have do be done by the embedder.

This also removes the queue used for outbound messages.

Renamed the class Message to CommandMessage as it is only used for debugger commands from the client. Related message queue classes has also been renamed.
Review URL: http://codereview.chromium.org/93118

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1788 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      8fefc769
  29. 22 Apr, 2009 1 commit
  31. 21 Apr, 2009 2 commits
  33. 20 Apr, 2009 2 commits
  35. 31 Mar, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Change handling of debugger unloading. · 1f7a7d9c
      sgjesse@chromium.org authored 
      Add a semaphore for accessing debugger varaibles which can be changed from a different thread. This is mainly the debug message handler which can be set to NULL to disconnect the debugger.

Control the unloading of the debugger from the V8 thread. Before the debugger unload was called from the thread setting the debug message handler to NULL. This was not safe as this involves calling into V8. This change handles the unloading of the debugger either when entering a debugger event and the debugger was disconnected while the debugger was not active or when leaving the debugger and the debugger was disconnected while the debugger was active.

Add a flag to avoid unloading the debugger if debugger code is used by the application for other purposes than debugging.

Added tests for clearing the debug message handler.
Review URL: http://codereview.chromium.org/56102

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1648 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      1f7a7d9c
  37. 27 Mar, 2009 3 commits
  39. 23 Mar, 2009 1 commit
  41. 19 Mar, 2009 1 commit
  43. 17 Mar, 2009 1 commit
  45. 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
  47. 06 Mar, 2009 2 commits
  49. 03 Mar, 2009 1 commit
  51. 19 Feb, 2009 2 commits
  53. 13 Feb, 2009 2 commits
  55. 09 Feb, 2009 1 commit