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).
Can you verify where the problem happens? I've recently written an
article that shows how to track this down:
http://www.linux-magazin.de/heft_abo/ausgaben/2007/01/getriebeschaden
(In German only, English version still embargoed).
-- Mike
Mike Schilli
[EMAIL PROTECTED]
>
> Have any problems with such a setup been reported before? (I wasn't able
> to find anything in the bug tracker or the mailing list archive)
>
> 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
>
-------------------------------------------------------------------------
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
