Hey, Perrin.

My DBI calls are within the code that is executed in the loop.  Not
before.  Even so, I tried using $dbh->super::disconnect(), and that had
no apparent affect.  Still segfaulting.

I'm feeling like it's not the DBI stuff.  Where else can I look?

Eric

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Perrin Harkins
> Sent: Tuesday, August 26, 2008 2:35 PM
> To: Berg, Eric
> Cc: modperl@perl.apache.org; [EMAIL PROTECTED]
> Subject: Re: Apache2/MP2/Parllel::ForkManager and Segmentation Faults
> 
> On Tue, Aug 26, 2008 at 2:28 PM, Berg, Eric 
> <[EMAIL PROTECTED]> wrote:
> > I'm using Apache::DBI.
> >
> > I stripped out calls to code that use DBI and it still segfaults.
> >
> > I've gone into the code and made sure that any method that 
> does a DBI
> > call also uses $dbh->disconnect;
> 
> With Apache::DBI, you actually need to call $dbh->SUPER::disconnect.
> However, you would only need to do this right before forking, not on
> every call.
> 
> - Perrin
> 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - -

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.

Reply via email to