On 9/5/06, Beheer <[EMAIL PROTECTED]> wrote:
We have an modperl2 (1.999.21) application that sometimes gives an
segmentation fault.
I'm having problems with getting Carp:Confess to work. When apache2
gives an segmentation fault, it only prints one line in the error log,
without the information where the segmentation fault originates. When I
induce an segmentation fault in our application
(Debug::DumpCore::segv();) the traceback works. Does anybody have a clue
how to get a more complete traceback?
The issue is: does apache2 reports the segmentation fault with
Carp::confess? If this is not the case, that's why you don't see the
stack trace information.
You may try Carp::Always, though I don't know if it will work within
mod_perl (I never tried it). If it works, it will turn every die/warn
into croak/carp with stack traces. It the segmentation fault is thrown
via die, you may able to see the information you want.
Regards,
Adriano Ferreira.
