[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    mod_perl2 + ModPerl::RegistryPrefork  + Test::Builder = segfault
From:       "Berg, Eric" <eric.berg () lehman ! com>
Date:       2008-09-04 22:09:21
Message-ID: 5CAFF755525FC5418CCF35FAEB2683BE12A31B09 () njpcmg1exms305 ! leh ! lbcorp ! lehman ! com
[Download RAW message or body]

Looks like we've narrowed the problem that I've described here
(http://mail-archives.apache.org/mod_mbox/perl-modperl/200808.mbox/%3c5C
AFF755525FC5418CCF35FAEB2683BE12A31A6C@njpcmg1exms305.leh.lbcorp.lehman.
com%3e)

It's something having to do with our use of Test::Builder.  Simplly
including Test::Builder in a CGI running under ModPerl::RegistryPrefork
causes it to segfault on a very regular basis.

Here's the message I posted on CPAN Forum for Test::Simple:

> > > > > > > > > > > > > > > 
Recently, during the process of porting all my apache 1.3/mod_perl 1.x
CGI's running under ModPerl::RegistryPrefork, I started running into
regular segfaults.  After a whole bunch of head scratching and testing,
we narrowed down the problem to our use'ing Test::Builder.

It appears to be some kind of conflict that might have to do with the
BEGIN code block that contains these lines for non-threaded Perl:

        *share = sub { return $_[0] };
        *lock  = sub { 0 };

I don't completely understand what these do in the context of
non-threaded apps, though they appear to be fairly innocuous at first
glance.

In any case, it's just using Test::Builder that causes Apache 2.2/mp2 to
segfault.

Many of our core modules contain test methods that are executed during
our CVS checkin process as regression tests, so we'd have to completely
redo our regression testing architecture to decouple Test::Builder from
our code.

Has anybody had any similar experience with this problem, or can you
help shed some light on the problem to help get us to a solution?
<<<<<<<<<<<<<<<

Has anybody seen this or anything like it before?

Eric
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \
-

This message is intended only for the personal and confidential use of the designated \
recipient(s) named above.  If you are not the intended recipient of this message you \
are hereby notified that any review, dissemination, distribution or copying of this \
message is strictly prohibited.  This communication is for information purposes only \
and should not be regarded as an offer to sell or as a solicitation of an offer to \
buy any financial product, an official confirmation of any transaction, or as an \
official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be \
secure or error-free.  Therefore, we do not represent that this information is \
complete or accurate and it should not be relied upon as such.  All information is \
subject to change without notice.

--------
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this \
communication (including any attachments) is not intended or written to be used and \
cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) \
promoting, marketing or recommending to another party any transaction or matter \
addressed herein.


[prev in list] [next in list] [prev in thread] [next in thread]