Changeset: https://hg.mozilla.org/integration/mozilla-inbound/rev/ac2b3068888b Steps to reproduce: mach mochitest-plain --no-autorun --debugger gdb dom/tests/mochitest/ajax/jquery/test_jQuery.html or ../obj-firefox/_virtualenv/bin/python ../obj-firefox/_tests/testing/mochitest/runtests.py --test-path=dom/tests/mochitest/ajax/jquery/test_jQuery.html --debugger=gdb in both cases, as soon as the app starts under gdb I get: Program exited with code 06. If I manually hack SetExceptionHandler in nsExceptionHandler.cpp to be a no-op, things work fine. Blocker, because debugging things is kind of necessary. :(
FWIW, build/automation.py does the right thing, but it looks like mochitest's runner doesn't use that anymore. So that looks like fallout from bug 746243
This is Mac? That's bug 914925. I have a patch there but I haven't figured out how to make it not break other things yet.
This is on Mac, yes. Is there at least something we could do to make it possible to manually tell the harness to turn off breakpad? Having to hack random C++ bits just to debug a reftest or mochitest is ... bad.
Depends on: 914925
Just set MOZ_CRASHREPORTER_DISABLE=1 in the environment. That's what automation.py does when you make it run a debugger. That's what mochitest harness should do too.
> Just set MOZ_CRASHREPORTER_DISABLE=1 in the environment env MOZ_CRASHREPORTER_DISABLE=1 ../mozilla/mach mochitest-plain --debugger gdb dom/tests/mochitest/ajax/jquery/test_jQuery.html ... Program exited with code 06. (gdb) Same thing with the manual runtests.py invocation. As in, something in the harness clobbers that env var, and I see no way to tell it not to do that.
is this still an issue, I know that nfroyd did some work on debuggers and mochitests in the last couple months.
This got fixed in bug 914925.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 914925
You need to log in before you can comment on or make changes to this bug.