Ryan Bloom wrote: > >Wild guess here, but look at line 827. and all the rest of the if statements >around it. Shouldn't all of those > >((type = exinfo->forced_type))) > >be > >((type == exinfo->forced_type))) > >I would bet that if they were, we would never hit that apr_pstrcat > Using == here would break the code, as it's uninitialized before the first of these expressions. --Brian
- Re: seg fault in 2.0.23 :-( Roy T. Fielding
- Re: seg fault in 2.0.23 :-( Ryan Bloom
- Re: seg fault in 2.0.23 :-( Brian Pane
- Re: seg fault in 2.0.23 :-( Ryan Bloom
- Re: seg fault in 2.0.23 :-( Roy T. Fielding
- Re: seg fault in 2.0.23 :-( William A. Rowe, Jr.
- Re: seg fault in 2.0.23 :-( Bill Stoddard
- Re: seg fault in 2.0.23 :-( Roy T. Fielding
- Re: seg fault in 2.0.23 :-( Bill Stoddard
- Re: seg fault in 2.0.23 :-( Brian Pane
- Re: seg fault in 2.0.23 :-( Ryan Bloom
- Re: seg fault in 2.0.23 :-( Bill Stoddard
- Re: seg fault in 2.0.23... Ryan Bloom
