393415 - automatically produce stacktraces on crash

Status: RESOLVED DUPLICATE of bug 387555

(Release Engineering :: General, defect)

Description

[Rob Campbell [:rc] (:robcee)]

Occasionally, the unittest machines crash. It would be nice to have stacktraces produced and emitted when this happens. This would require obtaining (and updating) stack processor on the machine, building symbols then running the processor on the minidump.

envvars: MOZ_AIRBAG=1, and MOZ_CRASHREPORTER_NO_REPORT=1

svn checkout http://google-breakpad.googlecode.com/svn/trunk/ google-breakpad

make -C objdir buildsymbols

minidump_stackwalk $profile/minidumps/$dumpfile $objdir/dist/crashreporter-symbols/$buildid

Note, at last check, the breakpad code required cygwin on windows and libcurl on linux.

Comment 1

[Nickolay_Ponomarev]

Is this different from bug 387555?

Comment 2

[Rob Campbell [:rc] (:robcee)]

Doesn't look like it. This bug was part of the discussion I had with Ted about environment variables used by the crashreporter initially and documented how to run the processor. I think we can close this and (we ran the processor a couple of times ad hoc) and leave the other to track the need for automatic crash reporting.

Comment 4

[(not currently active) Ted Mielczarek]

Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.