[gentoo-user] Crash dumps

2013-06-05 Thread Michael Mol
With some recent software updates (well, a month's worth...didn't
realize I wasn't syncing on my laptop), X now frequently dies on me.

As it happens, I've already rebuilt all the software on the system...I
do an emerge -e @world every time there's a gcc update. To my knowledge,
there's no old cruft, no old binaries, nothing for depclean to remove or
revdep-rebuild to fix, etc. etc.

The next step is to actually inspect the crashes and see what's
happening...but for this to be even remotely convenient, I'd like my
system to start accumulating crash dumps for my inspection. Fortunately,
I have -ggdb in CFLAGS for just such occasions, so I'm not wanting for
symbols...

Trouble is...I don't remember how to do this. How do I enable crash
dumps, and how do I control where the dump files are dropped?



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] Crash dumps

2013-06-05 Thread Paul Hartman
On Wed, Jun 5, 2013 at 1:09 PM, Michael Mol mike...@gmail.com wrote:
 With some recent software updates (well, a month's worth...didn't
 realize I wasn't syncing on my laptop), X now frequently dies on me.

 As it happens, I've already rebuilt all the software on the system...I
 do an emerge -e @world every time there's a gcc update. To my knowledge,
 there's no old cruft, no old binaries, nothing for depclean to remove or
 revdep-rebuild to fix, etc. etc.

 The next step is to actually inspect the crashes and see what's
 happening...but for this to be even remotely convenient, I'd like my
 system to start accumulating crash dumps for my inspection. Fortunately,
 I have -ggdb in CFLAGS for just such occasions, so I'm not wanting for
 symbols...

 Trouble is...I don't remember how to do this. How do I enable crash
 dumps, and how do I control where the dump files are dropped?

You may have already seen it, but this article may lend some clues:

http://www.gentoo.org/proj/en/qa/backtraces.xml