On Thursday 15 March 2007 11:18, Darryl Miles wrote:
> Torsten Foertsch wrote:
> > On Tuesday 13 March 2007 10:05, Torsten Foertsch wrote:
> > So, the simple patch below solves my problem. No segfaults so far. But is
> > it right?
> >
> > I have tested it with ab and several million requests and no
On Tuesday 13 March 2007 10:05, Torsten Foertsch wrote:
> I have found a reproducible way to segfault a mod_perled httpd.
Sorry for the private posting but I need advice from the person who has
implemented the worker mpm stuff in modperl particularly the "InterpScope
handler" stuff. I think that
On Tuesday 13 March 2007 10:05, Torsten Foertsch wrote:
> PerlInterpScope handler
I have had it run with "PerlTrace all" set. The xx attachment shows what
happens at the first run without segfault. yy shows the output with a
segfault. Obviously it dies after or in
modperl_module_config_obj_clean
Hi,
I have found a reproducible way to segfault a mod_perled httpd.
My environment:
httpd 2.2.3
mpm worker
mod_perl 2.0.3
perl 5.8.8 (Suse linux 10.2)
and my httpd.conf
LoadModule log_config_module "/opt/apache22-worker/li
Philip M. Gollucci wrote:
Stas Bekman wrote:
In case someone is interested in solving this config time segfault,
I've attached an A-T tarball that reproduces it. I've tried to merge
it into the mp2 test suite, but I can't reproduce it there, since
filterhandlers are already configured via htt
Stas Bekman wrote:
In case someone is interested in solving this config time segfault, I've
attached an A-T tarball that reproduces it. I've tried to merge it into
the mp2 test suite, but I can't reproduce it there, since filterhandlers
are already configured via httpd.conf and the stack is ini
In case someone is interested in solving this config time segfault, I've
attached an A-T tarball that reproduces it. I've tried to merge it into
the mp2 test suite, but I can't reproduce it there, since filterhandlers
are already configured via httpd.conf and the stack is initialized, so
mpxs_A
Stas Bekman wrote:
Philippe M. Chiasson wrote:
So, I guess I should just go ahead with my band-aid fix and we can worry
about the _real_ problem later then?
+1
Band-aid applied!
--
Philippe M. Chiasson m/gozer\@(apa
Philippe M. Chiasson wrote:
So, I guess I should just go ahead with my band-aid fix and we can worry
about the _real_ problem later then?
+1
--
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/
Geoffrey Young wrote:
Geoffrey Young wrote:
Before I go ahead and check that in, I'd like to at least get a bit more
feedback from the other folks that had been seeing this segfault, and
confirmation that this patch _does_ get rid of it.
I'll give it a whirl tonight.
whee! all tests pass.
Good,
Geoffrey Young wrote:
>>Before I go ahead and check that in, I'd like to at least get a bit more
>>feedback from the other folks that had been seeing this segfault, and
>>confirmation that this patch _does_ get rid of it.
>
>
> I'll give it a whirl tonight.
whee! all tests pass.
nice work.
>> I'll give it a whirl tonight. in truth, though, I forget exactly the
>> conditions that were causing it - I'm seeing a segfault now with
>> 2.0.47 (and
>> not 2.0.52) worker in the filter tests that is not reproducable when they
>> are run on their own.
>
>
> What filter test were failing ?
Geoffrey Young wrote:
Before I go ahead and check that in, I'd like to at least get a bit more
feedback from the other folks that had been seeing this segfault, and
confirmation that this patch _does_ get rid of it.
I'll give it a whirl tonight. in truth, though, I forget exactly the
conditions
> Before I go ahead and check that in, I'd like to at least get a bit more
> feedback from the other folks that had been seeing this segfault, and
> confirmation that this patch _does_ get rid of it.
I'll give it a whirl tonight. in truth, though, I forget exactly the
conditions that were causin
Stas Bekman wrote:
Philippe M. Chiasson wrote:
I spent quite a lot of time trying to figure out the root cause of this
problem
without much success. There is some strange interaction with
Perl_load_module()
that's causing this segfault.
I've rewritten that part to use eval_sv() instead and the
Philippe M. Chiasson wrote:
I spent quite a lot of time trying to figure out the root cause of this
problem
without much success. There is some strange interaction with
Perl_load_module()
that's causing this segfault.
I've rewritten that part to use eval_sv() instead and the segfault
vanished f
I spent quite a lot of time trying to figure out the root cause of this problem
without much success. There is some strange interaction with Perl_load_module()
that's causing this segfault.
I've rewritten that part to use eval_sv() instead and the segfault vanished for
me. As much as I'd like to na
Simon Hollier wrote:
Hi,
I moved up to mod_perl cvs snapshot ( should have done this before I
posted before as it fixed a header issue I was also having! D'oh! )
'make test' now passes everything except
ModPerl-Registry/t/cgi-bin/r_inherited.pl didn't have execution set and
thus one test failed (
Hi,
I moved up to mod_perl cvs snapshot ( should have done this before I
posted before as it fixed a header issue I was also having! D'oh! )
'make test' now passes everything except
ModPerl-Registry/t/cgi-bin/r_inherited.pl didn't have execution set and
thus one test failed ( This could just be m
Simon Hollier wrote:
I haven't looked at any code yet, nor done any debugging; but if someone
has any pointers here's the backtrace :
Simon, please show us a short test handler/script that we can reproduce the
problem with.
Starting program: /usr/local/apache/bin/httpd -DONE_PROCESS
[New Thread 1
I haven't looked at any code yet, nor done any debugging; but if someone
has any pointers here's the backtrace :
Starting program: /usr/local/apache/bin/httpd -DONE_PROCESS
[New Thread 1075546784 (LWP 845)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1075546784 (LWP
[Tulan, you have to keep the thread on the list. Please don't take it off list.]
[EMAIL PROTECTED] wrote:
Thanks for replying my question.
First let's get in sync: Are you using the latest cvs? or mod_perl 1.99?
I need to fix the bug report script to include that info.
I tried mod_perl 1.99_
[cc: changing a subject to something more suitable]
Tulan W. Hu wrote:
First let's get in sync: Are you using the latest cvs? or mod_perl 1.99?
I need to fix the bug report script to include that info.
Now you need to rebuild perl with debug support (using flags -Doptimize='-g'
-Dusedevel) so th
thanks for the debug info and test case guys.
root cause was that %ENV elements did not have proper magic assigned.
fixed in cvs.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Could you maybe send me your complet httpd.conf, see if I can just get
> the darn thing to segfault on me...
>
> Gozer out.
>
> > Bradley
> >
> > -- Forwarded message --
> > Date: Wed, 16 Oct 2002 13:37:50 +1000 (EST)
> > From: Bradley Baetz &l
On 17 Oct 2002, Philippe M. Chiasson wrote:
> On Thu, 2002-10-17 at 06:43, Bradley Baetz wrote:
> > Hmm, I wasn't subscribed to teh dev list, and this doesn't seem to have
> > made it to the archives. Sorry if people get this twice.
>
> I've tried to reproduce this with the same configurations
M. Chiasson <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: [mp2] segfault deleting ENV variable
>
> On 16 Oct 2002, Philippe M. Chiasson wrote:
>
> > On Tue, 2002-10-15 at 21:22, Bradley Baetz wrote:
> > > The following one line script will cause apac
Chiasson <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: [mp2] segfault deleting ENV variable
On 16 Oct 2002, Philippe M. Chiasson wrote:
> On Tue, 2002-10-15 at 21:22, Bradley Baetz wrote:
> > The following one line script will cause apache/mod_perl2 to segfault:
> >
On Tue, 2002-10-15 at 21:22, Bradley Baetz wrote:
> The following one line script will cause apache/mod_perl2 to segfault:
>
> delete @::ENV{'PATH'};
$ENV{'PATH'} would be slightly more modern ;-)
>
> I've tried this with both apache-2.0.40/mod_perl-1.99_05/perl-5.8.0 (ie
> stock RH8), and apa
29 matches
Mail list logo
