Skip to content

V
V8
Switch branch/tag
  1. 11 Aug, 2011 1 commit
  3. 08 Aug, 2011 2 commits
  5. 01 Aug, 2011 1 commit
  7. 26 Jul, 2011 1 commit
  9. 20 Jul, 2011 1 commit
  11. 14 Jul, 2011 1 commit
  13. 11 Jul, 2011 2 commits
  15. 29 Jun, 2011 3 commits
  17. 24 Jun, 2011 1 commit
  19. 22 Jun, 2011 1 commit
  21. 16 Jun, 2011 1 commit
  23. 10 Jun, 2011 2 commits
  25. 09 Jun, 2011 2 commits
  27. 08 Jun, 2011 1 commit
  29. 06 Jun, 2011 1 commit
  31. 31 May, 2011 1 commit
  33. 23 May, 2011 1 commit
  35. 18 Mar, 2011 3 commits
  37. 02 Mar, 2011 1 commit
  39. 01 Mar, 2011 1 commit
  41. 16 Feb, 2011 1 commit
    • antonm@chromium.org's avatar
      Properly process try/finally blocks. · 6b4ff18b
      antonm@chromium.org authored 
      In some circumstances, try/finally block can actually catch the exception:

function f() {
  try {
    throw 42;
  } finally {
    return 0;
  }
}

Therefore when propagating exception to v8::TryCatch, we must be sure
there is no try/finally blocks as well.

When bulding the messages we should be more conservative and expect that
any v8::TryCatch with no JS try/catch in between can potentionally
be the right exception handler.

Plus various minor refactorings.

BUG=1147
TEST=cctest/test-api/TryCatchAndFinallyHidingException, cctest/test-api/TryCatchAndFinally

Review URL: http://codereview.chromium.org/6526016

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6809 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      6b4ff18b
  43. 04 Jan, 2011 1 commit
  45. 03 Sep, 2010 1 commit
  47. 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
  49. 04 May, 2010 1 commit
  51. 16 Apr, 2010 1 commit
  53. 23 Mar, 2010 1 commit
  55. 03 Dec, 2009 1 commit
  57. 07 Sep, 2009 1 commit
  59. 04 Sep, 2009 3 commits