1. 27 Sep, 2010 1 commit
  2. 16 Sep, 2010 1 commit
  3. 31 Aug, 2010 1 commit
  4. 30 Aug, 2010 1 commit
  5. 17 Aug, 2010 2 commits
  6. 13 Aug, 2010 1 commit
  7. 11 Aug, 2010 1 commit
  8. 30 Jul, 2010 1 commit
  9. 29 Jul, 2010 4 commits
  10. 28 Jul, 2010 1 commit
  11. 14 Jul, 2010 1 commit
  12. 12 Jul, 2010 1 commit
  13. 06 Jul, 2010 1 commit
  14. 01 Jul, 2010 1 commit
  15. 30 Jun, 2010 1 commit
  16. 16 Jun, 2010 1 commit
  17. 10 Jun, 2010 1 commit
  18. 08 Jun, 2010 1 commit
    • sgjesse@chromium.org's avatar
      More precise break points and stepping when debugging · 634fb915
      sgjesse@chromium.org authored
      Added support for more precise break points when debugging and stepping. To achieve that additional nop instructions are inserted where breaking would otherwise be impossible. The number of nop instructions inserted are sufficient to make place for patching with a call to a debug break code stub. On Intel that is 5 nop's for 32-bit and 13 for 64-bit. Om ARM 3 nop instructions (12 bytes) are required.
      
      In order to avoid inserting nop's in to many places a simple ast checker have been added to check whether there are breakable code in a statement or expression. If it is possible to break in an expression no additional break enabeling code is inserted.
      
      Added break locations to the true and false part of a conditional expression.
      
      Added stepping tests to cover more constructs.
      
      These changes are only in the full compiler.
      
      Changed the default value for the option --debugger in teh d8 shell from true to false. The reason for this is that with --debugger turned on the full compiler will be used for all code in when running d8, which can be unexpeceted.
      
      Review URL: http://codereview.chromium.org/2693002
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4820 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      634fb915
  19. 07 Jun, 2010 1 commit
  20. 20 May, 2010 1 commit
  21. 06 May, 2010 1 commit
  22. 05 May, 2010 1 commit
  23. 28 Apr, 2010 1 commit
  24. 06 Apr, 2010 1 commit
  25. 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
  26. 23 Mar, 2010 3 commits
  27. 17 Mar, 2010 1 commit
  28. 12 Mar, 2010 1 commit
  29. 09 Mar, 2010 1 commit
    • kmillikin@chromium.org's avatar
      Small simplification of #include dependencies. · 3817a7ba
      kmillikin@chromium.org authored
      Remove messages.h from v8.h and include it explicitly in only the few places
      it is needed.  Many files relied on getting handles-inl.h implicitly from
      messages.h through v8.h, so include handles-inl.h explicitly in v8.h
      instead.
      
      Remove zone-inl.h from header files where it is not needed, can be replaced
      by a forward declaration, or can be replaced by zone.h (specifically,
      factory.h and heap.h).  Include zone.h or zone-inl.h in header files where
      it was implicitly included via heap.h or factory.h.  Prefer zone.h over
      zone-inl.h in header files where possible by including zone-inl.h in .cc
      files.
      
      Review URL: http://codereview.chromium.org/668248
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4058 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      3817a7ba
  30. 05 Mar, 2010 1 commit
  31. 01 Mar, 2010 1 commit
  32. 16 Feb, 2010 1 commit
  33. 08 Feb, 2010 2 commits