You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2003/05/06 11:42:24 UTC
Re: Perl segfault in 5.8
[redirecting to the right mailing list]
Arthur Bergman wrote:
> Hi,
>
> We are having a problem with weird segfaults in IO_flush. Reading old
> emails I see this
>
> http://mathforum.org/epigone/modperl/zhoolamgheld/
> Pine.LNX.4.33.0206131508310.955-100000@mako.covalent.net
>
> but this does not seem to be applied to libapreq, any reason why?
>
> Arthur
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
> For additional commands, e-mail: dev-help@perl.apache.org
Re: Perl segfault in 5.8
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Stas Bekman <st...@stason.org> writes:
> [redirecting to the right mailing list]
>
> Arthur Bergman wrote:
> > Hi,
> > We are having a problem with weird segfaults in IO_flush.
> > Reading old emails I see this
> > http://mathforum.org/epigone/modperl/zhoolamgheld/
> > Pine.LNX.4.33.0206131508310.955-100000@mako.covalent.net
> > but this does not seem to be applied to libapreq, any reason why?
> > Arthur
ISTR a pair of discussions, this being the first of the two.
I don't know why Doug didn't apply this patch, but I did apply
his other one.
Looking at the Request.xs code, it seems that we're duping the tempfile's
underlying file descriptor before handing it off to PerlIO. We
should flush the stdio buffers *before* doing that, but currently
I don't think we are.
OTOH, I'd expect a potential data-corruption problem here, not a
segfault. Have you got a test case or backtrace for us to look at?
--
Joe Schaefer