On Tue, 2006-09-05 at 09:25 -0300, Adriano Ferreira wrote:
> 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.
Yes, it does use Carp::Confess but stops confessing at the point where
Carp::Confess is called in the code. It looks like at that point carp
can't find the referring object (or something like that?).
Anybody a clue?
------------error log-------
(...)
SEGV traceback at /home/httpd/Application.pm line 138
Application::__ANON__('SEGV') called at -e line 0
eval {...} called at -e line 0
(...)
------------code-----------
(133) use Carp;
(134) use POSIX qw(SIGSEGV);
(135)
(136) POSIX::sigaction(
(137) SIGSEGV,
(138) POSIX::SigAction->new(sub { confess `date` . ": SEGV
traceback" })) or warn "Error setting SIGSEGV handler: $!\n";
------------system------------
Debian Sarge
Apache 2.0.54-5
Mod-perl2 1.999.21-1
