Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
V
V8
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Linshizhi
  • V8
  • Repository

Switch branch/tag
  • v8
  • test
  • inspector
  • debugger
  • debugger-statement.js
Find file
BlameHistoryPermalink
  • Kim-Anh Tran's avatar
    [debugger] Report hit breakpoints when stopping at a debugger statement · ccbe3217
    Kim-Anh Tran authored Nov 29, 2021
    Previously when hitting a debugger statement we would ignore reporting
    the hit breakpoints.
    
    Bug: chromium:1229541, chromium:1133307
    Change-Id: I47427a541391a27fc7783930e5e7eb41fbf2bb6a
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3306373Reviewed-by: 's avatarJaroslav Sevcik <jarin@chromium.org>
    Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#78145}
    ccbe3217
debugger-statement.js 1.06 KB
EditWeb IDE

Replace debugger-statement.js

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.