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
Specifically, a C++ assertion failure unrelated to the marionette tests, which results in crashing the process in DEBUG builds.
We've got a helpful mozdebug library in mozbase: https://dxr.mozilla.org/mozilla-central/rev/494289c72ba3997183e7b5beaca3e0447ecaf96d/testing/mochitest/runtests.py#2213
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
Assignee: ato → nobody
Status: ASSIGNED → NEW
For those looking for a temporary fix, I use a patch 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.  https://github.com/brendandahl/gecko/commit/73f78b6b68ebd2520e893ad221c4a34bd2dd1045
You need to log in before you can comment on or make changes to this bug.