Skip to content

V
V8
Switch branch/tag
  1. 25 Oct, 2016 1 commit
  3. 18 Oct, 2016 1 commit
  5. 17 Oct, 2016 1 commit
  7. 07 Oct, 2016 1 commit
  9. 28 Sep, 2016 1 commit
  11. 15 Sep, 2016 1 commit
  13. 07 Sep, 2016 1 commit
  15. 06 Sep, 2016 1 commit
    • marja's avatar
      Include only stuff you need, part 8: Fix debug.h -> liveedit.h. · 51a3ffd9
      marja authored 
      Rebuilding (after touching certain files) is crazy slow because
includes are out of control.

The (last remaining) offending include path is: ast.h <- liveedit.h <-
debug.h <- src/x64/assembler-whatever-port-inl.h <-
src/macro-assembler.h <- everything possible

With this CL, the rebuild steps needed when touching ast-value-factory.h
drops from 365 to 181.

BUG=v8:5294
TBR=bmeurer@chromium.org

Review-Url: https://codereview.chromium.org/2316443002
Cr-Commit-Position: refs/heads/master@{#39195}
      51a3ffd9
  17. 19 Aug, 2016 1 commit
  19. 12 Aug, 2016 3 commits
  21. 10 Aug, 2016 2 commits
    • yangguo's avatar
      [debugger] use source position to identify break points. · e2e676d5
      yangguo authored 
      This makes break point info independent from the code kind being executed.

BUG=v8:5265

Review-Url: https://codereview.chromium.org/2230143002
Cr-Commit-Position: refs/heads/master@{#38528}
      e2e676d5
    • yangguo's avatar
      Revert of [debugger] reapply break points after clearing one shots. (patchset... · 56b7a5fa
      yangguo authored 
      Revert of [debugger] reapply break points after clearing one shots. (patchset #1 id:1 of https://codereview.chromium.org/2221333002/ )

Reason for revert:
Found better solution.

Original issue's description:
> [debugger] reapply break points after clearing one shots.
>
> On the debug info, we have a list of existing break points.  When we
> step in the debugger, we flood the function with one-shot break points.
> Afterwards, we clear these one-shots by clearing all break locations.
>
> Previously, while clearing break locations, we would skip ones that have
> actual break points. Now we clear all break locations, and then reapply
> break points. This is necessary for the next step, when we encode break
> point info by source position, and not code offset. Encoding by code
> offset would mean that break points are dependent on the code kind we
> use.
>
> R=jgruber@chromium.org
> BUG=v8:5265
>
> Committed: https://crrev.com/808981a22ee19461bbe981ab33b58792d991533e
> Cr-Commit-Position: refs/heads/master@{#38492}

TBR=jgruber@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=v8:5265

Review-Url: https://codereview.chromium.org/2231653003
Cr-Commit-Position: refs/heads/master@{#38521}
      56b7a5fa
  23. 09 Aug, 2016 1 commit
    • yangguo's avatar
      [debugger] reapply break points after clearing one shots. · 808981a2
      yangguo authored 
      On the debug info, we have a list of existing break points.  When we
step in the debugger, we flood the function with one-shot break points.
Afterwards, we clear these one-shots by clearing all break locations.

Previously, while clearing break locations, we would skip ones that have
actual break points. Now we clear all break locations, and then reapply
break points. This is necessary for the next step, when we encode break
point info by source position, and not code offset. Encoding by code
offset would mean that break points are dependent on the code kind we
use.

R=jgruber@chromium.org
BUG=v8:5265

Review-Url: https://codereview.chromium.org/2221333002
Cr-Commit-Position: refs/heads/master@{#38492}
      808981a2
  25. 03 Aug, 2016 1 commit
    • neis's avatar
      [debug] Don't notify listener of exceptions internal to a desugaring. · f813494f
      neis authored 
      In the parser, we desugar yield* with the help of a regular yield. One
particular implementation detail of this desugaring is that when the user calls
the generator's throw method, this throws an exception that we immediately
catch. This exception should not be visible to the user, but through Devtools'
"Pause on Caught Exceptions" feature it used to be.

This CL extends the type of catch predictions with a new value for such internal
exceptions and uses that for the offending try-catch statement in yield*.  It
instruments the debugger to _not_ trigger an exception event in that case.

R=yangguo@chromium.org
TBR=littledan@chromium.org
BUG=v8:5218

Review-Url: https://codereview.chromium.org/2203803002
Cr-Commit-Position: refs/heads/master@{#38286}
      f813494f
  27. 25 Jul, 2016 1 commit
  29. 21 Jul, 2016 2 commits
  31. 30 Jun, 2016 1 commit
  33. 29 Jun, 2016 1 commit
  35. 28 Jun, 2016 2 commits
  37. 15 Jun, 2016 1 commit
  39. 14 Jun, 2016 3 commits
  41. 13 Jun, 2016 2 commits
  43. 08 Jun, 2016 1 commit
  45. 06 Jun, 2016 2 commits
  47. 03 Jun, 2016 1 commit
  49. 31 May, 2016 3 commits
  51. 27 May, 2016 1 commit
  53. 20 May, 2016 1 commit
    • ulan's avatar
      Workaround for glibc semaphore bug. · 84ee9470
      ulan authored 
      Instead of dynamically creating semaphore for each page parallel job,
we create one semaphore for MarkCompact and reuse it.

This patch also removes all instrumentation code that was added to
help with investigation.

BUG=chromium:609249
LOG=NO

Review-Url: https://codereview.chromium.org/1998213002
Cr-Commit-Position: refs/heads/master@{#36407}
      84ee9470
  55. 18 May, 2016 2 commits