I'm chasing a (difficult to reproduce) crash in SeaMonkey-2.17, for which upstream (Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=857162) would like to have a Mozilla crash-handler report -- accessible via the pseudo address "about:crashes". Even compiling SM with -ggdb and USE="debug" doesn't give me that option: how to do that? Reproducible: Sometimes
Please post your `emerge --info www-client/seamonkey' output in a comment.
Also, post the exact command's output and perhaps run a proper gdb backtrace on it.
(In reply to comment #0) > I'm chasing a (difficult to reproduce) crash in SeaMonkey-2.17, for which > upstream (Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=857162) would > like to have a Mozilla crash-handler report -- accessible via the pseudo > address "about:crashes". Even compiling SM with -ggdb and USE="debug" > doesn't give me that option: how to do that? > > Reproducible: Sometimes Please do not go around gentoo and file bugs upstream, you will get little to no help. You can get a proper bt using the gentoo useful backtrace guide. Once you provide this info I will look into it so we can fix the bug.
Sorry, I didn't mean to by-pass gentoo: I was filing other non gentoo-related bugs (addons & Co.), and, in a hurry, I forgot to respect the workflow for this one! I recompiled SeaMonkey-2.17 according to gentoo's debugging recommendations plus USE='debug' and saw it crashing after a while, but missed the 5 min delay to attach GDB to it. Then, I couldn't find any core dump, is it normal? In the past, without USE='debug', it used work... (I'll post any other useful info once I get a GDB backtrace.)
This is not happening any more with SM-2.20. I close it.