Hello list,
I have a segfault with a Pike that happens rarely on a busy Camas server. To get a backtrace and fill a bug report I've tried to run it into gdb however I didn't get any segfault for now and I can't run it into gdb for a long time since it is a production server (I saw this error only one time on the development server, too few traffic). Maybe it's not even possible to have a segfault inside gdb because of a strange side effects (maybe the segfault occurs only on a fast process or something).
So I'd like to know if it would be possible to catch SIGSEGV in Pike and output a backtrace so that:
. You might get more bug reports. . It would be possible to track problems when it's not possible to run inside a debugger or that the error don't happen in this case.
Thank you for your reply.
-- David Gourdelier