Add support for interactively debugging WPTs with upstream's `wpt run`.
`run_wpt_tests.py --verbose` ensures browser logs are dumped to stdout
so that `debug_renderer` can find the PID to attach to.
Bug: 1440021
Test: ./debug_renderer ./run_wpt_tests.py -t Default
Test: external/wpt/badging/badge-success.https.html
Change-Id: I58323aea67f6232bc28b198b8f18d3d7bb7d8a7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4893148
Reviewed-by: Weizhong Xia <weizhong@google.com>
Commit-Queue: Jonathan Lee <jonathanjlee@google.com>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1201810}
- Fix the broken link to gdbinit.md & lldbinit.md on linux/debugging.md.
- Additionally, replace the absolute link to gdbinit.md with a relative
link to maintain notation consistency with the other links in this
doc.
Bug: n/a
Change-Id: Idc275f63de05264b66d0fbe022f26dc0e0b63599
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4573957
Auto-Submit: Taiyo Mizuhashi <taiyo@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1150998}
Add a section at the top for build configuration. Move the gdbinit
instructions to the configuration section (it's required before
debugging) and remove the details about why this is required (it's
described on the dedicated page that's linked). Add a link to the
corresponding LLDB page.
Mention flag --gtest_break_on_failure for debugging tests.
Clarify LLDB install (the page used to imply that you had to run apt-get
to get the lldbinit file).
Change-Id: Ib292350ee521bf2bc3c4a836523fe070e4d7694e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4482817
Reviewed-by: Yuzhu Shen <yzshen@chromium.org>
Commit-Queue: Brett Wilson <brettw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1136698}
If debug_renderer detects that you're running web tests, modifies the
command line flags and adds appropriate run_web_tests flags for
debugging the renderer spawned for individual web tests.
Bug: None
Change-Id: I85980ff57c85738f8ad8d47e83ba9d61d5411e09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4198115
Commit-Queue: Robert Flack <flackr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1109686}
This adds the --wait-for-debugger-on-navigation flag which pauses
renderers when the target URL is known displaying a message for
each. The debug_renderer script is also updated to automatically
debug the site passed and unblock all other renderer processes.
Documentation in linux/debugging.md is updated to explain how
to use the updated script and flag.
Bug: 730065
Change-Id: I758bf6d10ba9b6a846d216987c20053d4c5ac240
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4028699
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Robert Flack <flackr@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1073426}
This CL enhances the --utility-startup-dialog switch to now take an
optional service sub type, and displays the subtype when waiting
for the debugger, or showing the dialog.
`chrome --utility-startup-dialog` works as before, prompting/pausing
for every utility process.
`chrome --utility-startup-dialog=data_decoder.mojom.DataDecoderService`
only prompts for the data decoder service.
We check for the switch first then interrogate its value to limit
any impact on normal startup time.
This should make it easier to debug specific utility processes.
Tests: manual tested on Windows & Linux
Change-Id: I0195432a9f826697a87c687406a30dbdf1bfa378
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2892176
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#882668}
This makes a few updates to the documentation on using the rr debugger:
* clarify recommendation to build from source into one about using a
recent version (which might mean building from source), and explain
why
* mention both rr replay -p and -f, and explain the difference
* remove reference to a year-old bug that's now subsumed by the advice
on using a recent version
* add advice on workarounds for calling functions that use LOG() from
gdb
* link to relevant Chromium Chronicle episode
Change-Id: I13206a009103ae12f83a3890101a91e02fd78a0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2794877
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#867753}