Mike Schilli wrote:
> On Mon, 6 Aug 2007, H. Meyer wrote:
>> I've just encountered very frequent segmentation faults when trying to
>> use Log4Perl in a perl web application running inside of apache 1.3.37
>> and mod_perl 1.29. I am using perl 5.8.8 and the latest Log4Perl
>> version from CPAN.
>
> Core dumps are unrelated to CPAN modules using plain Perl like Log4perl.
>
> If a core dump happens, the Perl interpreter perl crashes, which it
> shouldn't do if plain Perl is used (and not compiled .xs code).
We've been able to "fix" the issue for our local setup.
The following appender caused the segfaults:
log4perl.appender.STDERR=Log::Dispatch::Screen
log4perl.appender.STDERR.stderr=1
log4perl.appender.STDERR.layout=Log::Log4perl::Layout::PatternLayout
log4perl.appender.STDERR.layout.ConversionPattern=%d %-5p %5P %6X{uid}
%c:%M{1}:%L - %m%n
Corresponding apache error log entries:
DIED: Can't locate object method "DESTROY" via package
"Log::Dispatch::Screen" at
/usr/local/share/perl/5.8.8/Log/Log4perl/Logger.pm line 73.
[Mon Aug 6 11:29:18 2007] [notice] child pid 21957 exit signal
Segmentation fault (11)
Once that appender is disabled, everything (we currently only use
Log::Dispatch::File) works without problems.
Greetings
H. Meyer
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
log4perl-devel mailing list
log4perl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/log4perl-devel
