Skip to content

V
V8
Switch branch/tag
  1. 05 Aug, 2010 2 commits
  3. 28 Jul, 2010 1 commit
  5. 14 Jul, 2010 1 commit
  7. 01 Jul, 2010 1 commit
  9. 18 Jun, 2010 1 commit
    • sgjesse@chromium.org's avatar
      API: Resolve linker issues with using V8 as a DLL · 685cae60
      sgjesse@chromium.org authored 
      This changes the way the constants kJSObjectType, kFirstNonstringType and kProxyType are made available to the inlined part of the V8 API. This change to fixed constants resolves linker this linker error Windows

error LNK2001: unresolved external symbol "public: static int v8::internal::Internals::kJSObjectType" (?kJSObjectType@Internals@internal@v8@@2HA)

when linking against a V8 DLL.

This change also makes it possible to build all the C++ tests with ENABLE_DEBUGGER_SUPPORT not defined. Now C++ tests run ENABLE_DEBUGGER_SUPPORT not defined, and only the JavaScript tests which tests the debugger fails when ENABLE_DEBUGGER_SUPPORT is not defined.
Review URL: http://codereview.chromium.org/2820016

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@4898 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      685cae60
  11. 17 Jun, 2010 1 commit
  13. 16 Jun, 2010 1 commit
  15. 15 Jun, 2010 1 commit
  17. 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
  21. 04 Jun, 2010 1 commit
  23. 20 May, 2010 1 commit
  25. 06 May, 2010 1 commit
  27. 28 Apr, 2010 4 commits
  29. 19 Apr, 2010 1 commit
  31. 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
  33. 23 Feb, 2010 1 commit
  35. 16 Feb, 2010 1 commit
  37. 10 Feb, 2010 1 commit
  39. 29 Jan, 2010 1 commit
  41. 26 Jan, 2010 1 commit
  43. 25 Jan, 2010 1 commit
  45. 21 Jan, 2010 3 commits
  47. 20 Jan, 2010 2 commits
  49. 19 Jan, 2010 3 commits
  51. 18 Jan, 2010 1 commit
  53. 15 Jan, 2010 2 commits
  55. 15 Dec, 2009 2 commits
  57. 27 Nov, 2009 1 commit