1. 16 May, 2011 1 commit
  2. 22 Mar, 2011 1 commit
  3. 18 Mar, 2011 3 commits
  4. 07 Dec, 2010 2 commits
  5. 04 Nov, 2010 1 commit
  6. 27 Sep, 2010 1 commit
  7. 14 Jul, 2010 1 commit
  8. 20 May, 2010 1 commit
  9. 24 Mar, 2010 1 commit
    • pfeldman@chromium.org's avatar
      Expose debug context into the native code. This change is doing several things: · 54f0a5b2
      pfeldman@chromium.org authored
      1) Exposes Local<Context> v8::Debug::GetDebugContext().
      Rationale: We can already get debugger context instance using various workarounds,
      so exposing it explicitly in the API only makes things more clear.
      
      2) Removes debugger.HasJavaScriptFrames() requirement for entering debugger context.
      Rationale: Sometimes we'd like to call into debugger from the external native code.
      
      3) Makes Debugger v8::Debug::Call execute on debugger context's global object.
      Rationale: This is somewhat arguable, but temporary measure. We've agreed that we
      should introduce a DebugAPI object that would expose necessary API in the debug-delay.
      The problem is that it would take some time to define this API and it is not really
      convenient to do that on the v8 land given the difference in v8 / host lifecycle.
      The plan is to compose this API as a Debug.* wrapper outside v8 by means of exposing
      debugger context's global object here, and once API settles down, upstream it to v8 and
      start making Debug::Calls on this new DebugAPI object instead.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4251 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      54f0a5b2
  10. 18 Jan, 2010 1 commit
  11. 15 Jan, 2010 1 commit
  12. 18 Dec, 2009 1 commit
  13. 14 Dec, 2009 1 commit
  14. 13 Dec, 2009 1 commit
  15. 18 Nov, 2009 1 commit
  16. 17 Aug, 2009 1 commit
  17. 05 Aug, 2009 1 commit
  18. 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
  19. 04 May, 2009 1 commit
  20. 29 Apr, 2009 5 commits
  21. 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
  22. 22 Apr, 2009 1 commit
  23. 21 Apr, 2009 1 commit
  24. 27 Mar, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Debugger message handler can be called from V8 thread. · 8b7a288e
      sgjesse@chromium.org authored
      The message handler function set through the debugger API is normally called in a different thread than the V8 thread where execution is stopped due to debugger event. This change adds an option to the API for specifying that the message handler should be called directly from the V8 thread. For an application like Chrome where thread dispatching is already in place this makes more sense.
      
      Add an option to the message handler debugger API to process messages in the thread where V8 is running instead of posting it to a queue for processing on a additional thread.
      Review URL: http://codereview.chromium.org/42643
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1627 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      8b7a288e
  25. 23 Mar, 2009 1 commit
  26. 03 Mar, 2009 1 commit
  27. 19 Feb, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Add host callback for debug break. · 44b83d3e
      sgjesse@chromium.org authored
      Add the ability to have the host embedding V8 receive a callback in the V8 thread while V8 is processing a debug callback. When V8 is processing a debug callback the thread where V8 is executing is sitting in a tight loop processing debug commands until the continue command has been executed. In some embedding situations it is beneficial to be able to call back into the embedding host from the thread where V8 is sitting. The might have functions which needs to be called to complement the JavaScript debugging.
      
      Using the uint16_t array to pass a void* is a temporary hack.
      Review URL: http://codereview.chromium.org/20491
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1318 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      44b83d3e
  28. 03 Feb, 2009 1 commit
  29. 27 Nov, 2008 1 commit
  30. 07 Nov, 2008 1 commit
  31. 09 Sep, 2008 1 commit
  32. 08 Sep, 2008 1 commit
  33. 04 Sep, 2008 1 commit