1. 18 Jul, 2018 1 commit
    • Yang Guo's avatar
      Reland "[builtins] Add %IsTraceCategoryEnabled and %Trace builtins" · 0dd33901
      Yang Guo authored
      This is a reland of 8d4572a2
      
      Original change's description:
      > [builtins] Add %IsTraceCategoryEnabled and %Trace builtins
      >
      > Adds the builtin Trace and IsTraceCategoryEnabled functions
      > exposed via extra bindings. These are intended to use by
      > embedders to allow basic trace event support from JavaScript.
      >
      > ```js
      > isTraceCategoryEnabled('v8.some-category')
      >
      > trace('e'.charCodeAt(0), 'v8.some-category',
      >       'Foo', 0, { abc: 'xyz'})
      > ```
      >
      > Bug: v8:7851
      > Change-Id: I7bfb9bb059efdf87d92a56a0aae326650730c250
      > Reviewed-on: https://chromium-review.googlesource.com/1103294
      > Commit-Queue: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Yang Guo <yangguo@chromium.org>
      > Reviewed-by: Fadi Meawad <fmeawad@chromium.org>
      > Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      > Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#54121}
      
      TBR=cbruni@chromium.org
      
      Bug: v8:7851
      Change-Id: Id063754b2834b3b6a2b2654e76e8637bcd6aa5f8
      Reviewed-on: https://chromium-review.googlesource.com/1137071
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
      Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#54532}
      0dd33901
  2. 16 Jul, 2018 1 commit
  3. 02 Jul, 2018 3 commits
  4. 05 Jun, 2018 1 commit
  5. 29 May, 2018 1 commit
  6. 16 May, 2018 1 commit
  7. 09 May, 2018 1 commit
  8. 01 May, 2018 1 commit
  9. 24 Apr, 2018 1 commit
  10. 17 Apr, 2018 1 commit
    • Ingvar Stepanyan's avatar
      Report late-bound scripts to the debugger · 1dcd1c9f
      Ingvar Stepanyan authored
      Previously, if an unbound script was created in a non-inspected context,
      but later bound to an inspected one, it never appeared in the
      debugger sources.
      
      After this change `OnAfterCompile` will be invoked not on the original
      script compilation, but when it's actually bound to a context for
      execution, which means `Debugger.scriptParsed` will be now sent to the
      inspector even for such precompiled scripts.
      
      R=jgruber@chromium.org, kozyatinskiy@chromium.org, yangguo@chromium.org
      
      Bug: v8:7654
      Change-Id: Ice13312e425903fb2baf14edab5c566d649a6438
      Reviewed-on: https://chromium-review.googlesource.com/1013581Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52652}
      1dcd1c9f
  11. 13 Apr, 2018 1 commit
  12. 10 Apr, 2018 1 commit
    • Matheus Marchini's avatar
      interpreter: make interpreted frames distinguishable in the native stack · ada64b58
      Matheus Marchini authored
      Before Turbofan/Ignition it was possible to use external profilers to
      sample running V8/Node.js processes and generate reports/FlameGraphs
      from that. It's still possible to do so, but non-optimized JavaScript
      functions appear in the stack as InterpreterEntryTrampoline. This commit
      adds a runtime flag which makes interpreted frames visible on the
      process' native stack as distinguishable functions, making the sampled
      data gathered by external profilers such as Linux perf and DTrace more
      useful.
      
      R=bmeurer@google.com, franzih@google.com, jarin@google.com, yangguo@google.com
      
      Bug: v8:7155
      Change-Id: I3dc8876aa3cd9f1b9766624842a7cc354ccca415
      Reviewed-on: https://chromium-review.googlesource.com/959081
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#52533}
      ada64b58
  13. 05 Apr, 2018 1 commit
  14. 08 Mar, 2018 1 commit
  15. 08 Feb, 2018 1 commit
  16. 22 Jan, 2018 1 commit
  17. 16 Jan, 2018 1 commit
  18. 11 Jan, 2018 1 commit
  19. 10 Jan, 2018 2 commits
  20. 07 Jan, 2018 1 commit
  21. 04 Jan, 2018 1 commit
  22. 21 Dec, 2017 1 commit
  23. 19 Dec, 2017 1 commit
  24. 10 Dec, 2017 1 commit
  25. 24 Nov, 2017 1 commit
  26. 20 Nov, 2017 1 commit
  27. 18 Nov, 2017 1 commit
    • Anna Henningsen's avatar
      [api] Make running scripts in AddMessageListener callback work in debug mode · 09b53eef
      Anna Henningsen authored
      The existance of an `AllowJavascriptExecutionDebugOnly` scope in
      `Isolate::ReportPendingMessages()` indicates that the API supports
      running arbitrary JS code in a `AddMessageListener` callback.
      
      Currently, this can fail in debug mode: The
      `!isolate->external_caught_exception()` condition is checked when
      entering API methods inside such a handler. However, if there is
      a verbose `TryCatch` active when the exception occurs, this
      check fails, and when calling `ToString()` on the exception object
      leaves a pending exception itself, the flag is re-set to `true`.
      
      Fix this problem by clearing the flag and the pending exception if
      there was one during `ToString()`. This matches the code a few lines
      up in `messages.cc`, so the exception state is now consistent
      during the callback.
      
      This currently makes a Node.js test fail in debug mode
      (`parallel/test-error-reporting`).
      
      Bug: node:7144
      Bug: node:17016
      Change-Id: I060d00fea3e9a497f4df34c6ff8d6e29ebe96321
      Reviewed-on: https://chromium-review.googlesource.com/718096
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49466}
      09b53eef
  28. 17 Nov, 2017 1 commit
    • Jakob Gruber's avatar
      Revert "[coverage] add coverage for binary expressions" · 9037639e
      Jakob Gruber authored
      This reverts commit 4d3bc552.
      
      Reason for revert: https://crbug.com/785778
      
      Original change's description:
      > [coverage] add coverage for binary expressions
      > 
      > Adds block-level coverage tracking for binary && and ||
      > expressions. Introduces a BinaryOperation source-range
      > for tracking the operations themselves and an Expression
      > source-range, used for tracking NaryLogical expressions.
      > 
      > This builds on work by jgruber@chromium.org in
      > the issue.
      > 
      > TBR=marja@chromium.org
      > R=​jgruber@chromium.org, rmcilroy@chromium.org
      > 
      > Bug: v8:6660
      > Change-Id: I83a81f13a3514a734c06948b2d3e91138fb00e18
      > Reviewed-on: https://chromium-review.googlesource.com/754564
      > Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
      > Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#49304}
      
      TBR=rmcilroy@chromium.org,marja@chromium.org,jgruber@chromium.org,ben@npmjs.com
      
      # Not skipping CQ checks because original CL landed > 1 day ago.
      
      Bug: v8:6660
      Change-Id: Ie017c528604b2e01400f527511413eaea5786198
      Reviewed-on: https://chromium-review.googlesource.com/776768Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#49454}
      9037639e
  29. 10 Nov, 2017 1 commit
  30. 07 Nov, 2017 1 commit
  31. 20 Oct, 2017 2 commits
  32. 13 Oct, 2017 1 commit
  33. 04 Oct, 2017 1 commit
  34. 28 Sep, 2017 1 commit
  35. 28 Aug, 2017 1 commit
  36. 23 Aug, 2017 1 commit