On Tue, Sep 18, 2018 at 04:55:07PM +1200, Tim Makarios wrote: > On 13/09/18 21:23, Mike Hommey wrote: > > Huh. Can you then try ulimit -c unlimited, and upload the resulting core > > file somewhere? > > I'm not sure I quite understand you here. I ran > > $ ulimit -c unlimited > $ firefox-esr > > The output was: > > > ExceptionHandler::GenerateDump cloned child 1472 > > ExceptionHandler::SendContinueSignalToChild sent continue signal to child > > ExceptionHandler::WaitForContinueSignal waiting for continue signal... > > and a window popped up inviting me to choose whether to report the crash to > Mozilla, and whether to quit or restart Firefox. > > I couldn't find any resulting core file. Where is it meant to be?
Oh, right. Forgot about the crash reporter interposing itself. You can do one of the following: - set MOZ_CRASHREPORTER_DISABLE to 1 in the environment and try again - or send the report to Mozilla, and find its id in ~/.mozilla/firefox/Crash Reports/submitted - or attach the crash report data from ~/.mozilla/firefox/Crash Reports/pending (both the .dmp and the .extra with the same id; only the last pair) I'd suggest the second one, in case your session crashed at some point where some private data might have been on the stack. That would limit the number of people who can look at the data, while attaching the raw data to the bug would make it public. Or the third one, if you send the files to me rather than the bug (that would also be smaller to transfer than a full core). Thanks Mike
