1. 18 Dec, 2013 1 commit
  2. 22 Nov, 2013 1 commit
  3. 26 Sep, 2013 1 commit
  4. 11 Jul, 2013 1 commit
  5. 09 Jul, 2013 1 commit
  6. 05 Jun, 2013 1 commit
  7. 29 May, 2013 1 commit
  8. 02 May, 2013 1 commit
  9. 15 Mar, 2013 1 commit
  10. 25 Jan, 2013 1 commit
  11. 13 Nov, 2012 1 commit
  12. 19 Jun, 2012 1 commit
  13. 30 Mar, 2012 1 commit
  14. 02 Sep, 2011 1 commit
  15. 19 Aug, 2011 1 commit
  16. 14 Jul, 2011 2 commits
  17. 30 Jun, 2011 1 commit
  18. 29 Jun, 2011 1 commit
  19. 10 Jun, 2011 3 commits
  20. 06 Jun, 2011 1 commit
  21. 30 May, 2011 1 commit
  22. 18 May, 2011 1 commit
  23. 29 Apr, 2011 1 commit
  24. 21 Apr, 2011 1 commit
  25. 07 Apr, 2011 1 commit
  26. 06 Apr, 2011 1 commit
  27. 01 Apr, 2011 1 commit
  28. 30 Mar, 2011 1 commit
  29. 24 Mar, 2011 2 commits
  30. 21 Mar, 2011 1 commit
  31. 18 Mar, 2011 3 commits
  32. 10 Mar, 2011 1 commit
  33. 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
  34. 08 Dec, 2010 1 commit