RE: trying to add header field using PerlInputFilterHandler to proxy packets

2009-07-14 Thread Brandon Allgood
FYI, this answered my question and everything is working. thanks, Brandon -Original Message- From: Torsten Foertsch [mailto:torsten.foert...@gmx.net] Sent: Tuesday, June 30, 2009 1:00 AM To: modperl@perl.apache.org Cc: Brandon Allgood Subject: Re: trying to add header field using PerlIn

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
On Tue, Jul 14, 2009 at 4:56 PM, Perrin Harkins wrote: > You might want to try mod_log_forensic to see what the request was > that crashed it. cool! Will look into that tomorrow (at home now) thanks! -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author o

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Perrin Harkins
Alan, You might want to try mod_log_forensic to see what the request was that crashed it. - Perrin On Tue, Jul 14, 2009 at 3:29 PM, Alan McKay wrote: >> http://modperlbook.org/html/21-5-8-Noninteractive-Perl-Debugging-Under-mod_perl.html > > OK, I'm doing this, but it seems that the file it prod

Re: graceful restarts, modperl and pre-loaded modules

2009-07-14 Thread Perrin Harkins
On Tue, Jul 14, 2009 at 3:25 PM, Philippe M. Chiasson wrote: >> Graceful restart used to just re-read the >> conf, not restart the perl interpreter. > > Now I believe it does, and it's easy to verify. > > A loaded PerlModule will get reloaded on graceful restart, that's for sure. That won't be eno

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
> http://modperlbook.org/html/21-5-8-Noninteractive-Perl-Debugging-Under-mod_perl.html OK, I'm doing this, but it seems that the file it produces only ever gets up to 7.3M and that's it. I'm guessing it is because when httpd forks off all the children, they do not record to this file anymore. So

Re: graceful restarts, modperl and pre-loaded modules

2009-07-14 Thread Philippe M. Chiasson
On 14/07/09 15:00 , Perrin Harkins wrote: > On Tue, Jul 14, 2009 at 2:36 PM, Philippe M. > Chiasson wrote: >> On a gracefull restart, all perl interpreters are shutdown and new, >> clean ones replace them, reloading any module you configure for preloading. > > I don't think this is right, Philippe

Re: graceful restarts, modperl and pre-loaded modules

2009-07-14 Thread Perrin Harkins
On Tue, Jul 14, 2009 at 2:36 PM, Philippe M. Chiasson wrote: > On a gracefull restart, all perl interpreters are shutdown and new, > clean ones replace them, reloading any module you configure for preloading. I don't think this is right, Philippe, unless something has changed with it in mod_perl 2

Re: graceful restarts, modperl and pre-loaded modules

2009-07-14 Thread Philippe M. Chiasson
On 14/07/09 14:04 , E R wrote: > Hi, > > I was wondering how graceful restarts of apache interact with modperl > and "pre-loaded" modules. > > Specifically, if the apache parent process loads module Foo.pm, and I > modify Foo.pm, can I use a graceful restart to get the apache parent > to read the

graceful restarts, modperl and pre-loaded modules

2009-07-14 Thread E R
Hi, I was wondering how graceful restarts of apache interact with modperl and "pre-loaded" modules. Specifically, if the apache parent process loads module Foo.pm, and I modify Foo.pm, can I use a graceful restart to get the apache parent to read the new version of Foo.pm? Thanks, ER

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
> I have had to debug these things before, and they're very painful!  I > usually end up commenting out half the code at a time to narrow things > down, and it's never what I expect.  Usually it's a module with a > compiled library, i.e. not a pure-Perl module. Well, the really crummy thing is tha

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Scott Gifford
Alan McKay writes: > Here is what I am doing based on the mod-perl debugging page I > referred to in my first email. I basically load the core dump in > gdb, and then alternately do "up" and "curinfo" on each line shown. > Sometimes I end up with what I got here where I get to a certain point >

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
OK, not much response from the list :-( More googling and I'm trying this now : http://modperlbook.org/html/21-5-8-Noninteractive-Perl-Debugging-Under-mod_perl.html Will keep y'all posted ... -- “Don't eat anything you've ever seen advertised on TV” - Michael Pollan, author of "In De

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
Here is what I am doing based on the mod-perl debugging page I referred to in my first email. I basically load the core dump in gdb, and then alternately do "up" and "curinfo" on each line shown. Sometimes I end up with what I got here where I get to a certain point and it says "cannot access mem

Re: first time debugging apache/mod_perl Seg fault

2009-07-14 Thread Alan McKay
Unfortunately it seems we are already up to the latest and greatest : Bundle Bundle::DBI (T/TI/TIMB/DBI-1.609.tar.gz) Module DBI (T/TI/TIMB/DBI-1.609.tar.gz) Any further help on slugging through this? On Mon, Jul 13, 2009 at 8:22 PM, Alan McKay wrote: > Oh, the