Re: [PATCH]Re: segfault analysis

2007-05-14 Thread Philippe M. Chiasson
Torsten Foertsch wrote: > On Sunday 06 May 2007 19:11, Torsten Foertsch wrote: >> I am in the middle of the analysis of a segfault. The segfault happens in a >> $r->push_handlers(PerlFixupHandler=>sub{}). Unfortunately it happens not >> for every request but after 13. Finally, I think I have tracke

Re: [PATCH]Re: segfault analysis

2007-05-07 Thread Torsten Foertsch
On Monday 07 May 2007 19:19, Philippe M. Chiasson wrote: > Torsten Foertsch wrote: > > On Sunday 06 May 2007 19:11, Torsten Foertsch wrote: > >> [...] > > > > That happens if there is no handler configured at startup time but more > > than one for the same phase at request time. > > if (ra

Re: [PATCH]Re: segfault analysis

2007-05-07 Thread Philippe M. Chiasson
Torsten Foertsch wrote: > On Sunday 06 May 2007 19:11, Torsten Foertsch wrote: >> [...] > > That happens if there is no handler configured at startup time but more than > one for the same phase at request time. if (ravp && !*ravp) { + /* initialize ravp either from avp or as a

[PATCH]Re: segfault analysis

2007-05-07 Thread Torsten Foertsch
On Sunday 06 May 2007 19:11, Torsten Foertsch wrote: > I am in the middle of the analysis of a segfault. The segfault happens in a > $r->push_handlers(PerlFixupHandler=>sub{}). Unfortunately it happens not > for every request but after 13. Finally, I think I have tracked it down to > something to t