1705093 - Stop dumping oodles of stuff into stderr/stdout for local build crashes

Status: NEW

(Testing :: General, defect, P3)

Description

[:Gijs (he/him)]

When my local builds on Windows crash in the parent process they dump stacks for every thread, plus all the loaded modules, and basically use up most of the backscroll of my terminal app, making it impossible to find what happened right before the crash. This is not nice.

I imagine the info may be useful on try/infra? But especially locally for artifact builds, the stacks aren't even useful, I get stuff like:

 9  xul.dll + 0x9c6df5
    rsp = 0x0000002847dff910   rip = 0x00007ff8c4cb6df5
    Found by: stack scanning

which tells me nothing.

Comment 1

[Mike Hommey [:glandium]]

Huh, that's not the kind of crash dump I was thinking you were seeing. That is a dump of crash minidumps, and that's handled by the test harness, IIRC.