httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <ch...@topsail.org>
Subject Re: [STATUS] Monday, April 7, 05:05am PDT
Date Tue, 08 Apr 1997 13:43:08 GMT
Jim Jagielski wrote:
> 
> Roy T. Fielding wrote:
> >
> > 1.2 Showstoppers with no patches yet:
> >
> >   * redirect of index file causes SEGV [Marc]
> >       Status: have a way to stop the core dump, but that doesn't make
> >       it work properly.
> >       See also: <Pine.BSF.3.91.970210204402.12197B-100000@localhost.imdb.com>
> >
> >   * SEGV under FreeBSD, Next with lingering_close [and proxy?]
> >       <3331034D.167EB0E7@topsail.org>
> >         Chuck says: Roy's latest timeout patches have stopped the lingering
> >         close notifications, but the core dumps continue. The dumped image
> >         is so trashed that it can't be backtraced. I believe the reason we
> >         haven't seen more reports is that FreeBSD and perhaps Linux are
> >         disabling core dumps by default as a security measure.
> 
> NeXT now no longer uses l_c() so that's a ugly "fix". I hope to get
> a FreeBSD machine up and running this week to run Apache on... Is the
> problem 2.1.6, 2.1.7 or 2.2.1 (or all?)

Not a fix; an observation. I'm testing some proxy fixes here that appear
to fix the remaining SIGSEGVs that I'm seeing, basically making the
error handling on transmission errors consistent, related to PR #45 and
#314.
-- 
chuck
Chuck Murcko
The Topsail Group, West Chester PA USA
chuck@topsail.org

Mime
View raw message