On Thu, Apr 11, 2002 at 05:21:24PM -0400, Kevin A. McGrail wrote: > > Date: Fri, 12 Apr 2002 00:24:11 +0800 > > To: [EMAIL PROTECTED] > > From: Stas Bekman <[EMAIL PROTECTED]> > > Subject: Challenging things to do: SIGSEGV catcher and backtrace extractor > > Message-ID: <[EMAIL PROTECTED]> > > > > A few moons ago we have discussed on the dev list a tool for automatic > > segfault detection (including multiple segfaults during 'make test') and > > core backtrace generation. I'm quite frankly tired of explaining again > > and again that we need a core file backtrace, how to get the core file > > dumped and generating trace (no offense, just facts). I'm sure there is > > a better way to do. If we can automate this process, like many other > > apps do (e.g. gnome/kde apps) this will save us a lot of traffic on the > > list and frustration on users' behalf and make us all happier. > > While I can't step up to the plate to help on development because I am still working >on GETTING a > core file, I can second the motion. The frustration in getting a good working core >file to trace > has been enormous and I am neither a newbie nor someone who gives up easily. > > Regards, > KAM
# whoami root # chmod 777 / The above is necessary in certain scenarios in order to get a core file from httpd. If you're still not getting a core file (in the / directory), check your shell process's core file limit (see the "ulimit" or "limit" section of your favorite shell's man page on how to change this). -- \_/} Mark P. Fister Java, Java, everywhere, and all \_/} \_/} eBay, Inc. the cups did shrink; Java, Java \_/} \_/} Austin, TX everywhere, nor any drop to drink! \_/}
