Add --debugger [gdb|lldb|rr|...] flag to marionette runner and mach

NEW
Unassigned

Status

Testing
Marionette
P3
normal
2 years ago
13 days ago

People

(Reporter: fitzgen, Unassigned)

Tracking

(Depends on: 1 bug, {ateam-marionette-client})

Firefox Tracking Flags

(Not tracked)

Details

I am debugging an assertion failure where my only reproducible test case is running marionette tests and this is really annoying to debug with gdb because I have to try to find and attach to the process before it ends.

Would be a lot easier if I could add `--debugger gdb` when running marionette tests.
Assignee: nobody → ato
Status: NEW → ASSIGNED
Keywords: ateam-marionette-client
Specifically, a C++ assertion failure unrelated to the marionette tests, which results in crashing the process in DEBUG builds.
Btw this is no only mach which is missing this flag. But also the runner doesn't have it yet.
Summary: Add --debugger [gdb|lldb|rr|...] flag to `./mach marionette-test` → Add --debugger [gdb|lldb|rr|...] flag to marionette runner and mach
Unassigning myself.
Assignee: ato → nobody
Status: ASSIGNED → NEW

Updated

11 months ago
Depends on: 958475
Duplicate of this bug: 853264
Priority: -- → P3
Duplicate of this bug: 1412058

Comment 7

4 months ago
For those looking for a temporary fix, I use a patch[1] that adds MOZ_DEBUG_PARENT_PROCESS (similar to MOZ_DEBUG_CHILD_PROCESS), where gecko dumps the process id and waits for a debugger to attach.


[1] https://github.com/brendandahl/gecko/commit/73f78b6b68ebd2520e893ad221c4a34bd2dd1045
Priority: P3 → P1
Priority: P1 → P3
Version: Version 3 → unspecified
You need to log in before you can comment on or make changes to this bug.