Date: Fri, 24 Jul 2009 01:15:04 +0200 (CEST) From: Alexander Best <alexbestms@math.uni-muenster.de> To: <freebsd-current@freebsd.org> Subject: Re: core dumps being overwritten Message-ID: <permail-200907232315041e86ffa800004dc4-a_best01@message-id.uni-muenster.de>
next in thread | raw e-mail | index | archive | help
i was thinking about this issue the other day again. if /var/crash/bounds gets
corrupted vital crash/debug information could be lost (like in my case).
why don't we check for existing core dumps instead of using bounds? doing
something like in this pseudo code:
i = 0;
while(exist("vmcore."i) || exist("core.txt."i) || exist("info."i))
i++;
write("vmcore."i);
write(""core.txt."i);
write("info."i);
or how about using /dev/random to create unique filenames so core dumps never
get overwritten?
cheers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?permail-200907232315041e86ffa800004dc4-a_best01>