Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
From: "Rob Saccoccio" <robs@fastcgi.com>
To: "David Reid" <dreid@jetnet.co.uk>,
	<dev@apr.apache.org>
Subject: RE: New poll code
Date: Fri, 2 Aug 2002 19:23:00 -0400
Message-ID: <KIEMJLOLKLPOPKIBCELNIECCEOAA.robs@fastcgi.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <000801c23a58$74555e40$7300a8c0@MITHRIL>

I posted a patch or two to ab to dev@httpd a week or two back.  At the time
I didn't realize the poll code was in flux (but noticed shortly after).

I actually have additional changes to submit but wanted to wait for the poll
api to stablize.

I'll bring it up to date and post it a little later tonight.

--rob

> -----Original Message-----
> From: David Reid [mailto:dreid@jetnet.co.uk]
> Sent: Friday, August 02, 2002 3:12 PM
> To: dev@apr.apache.org
> Subject: New poll code
>
>
> New poll test works fine on beos and apache builds OK but ab -n1000 -c2
> crashes with a segfault in apr_poll.
>
> Off on hols so can't diagnose further - sorry.
>
> david
>
> ----- Original Message -----
> From: "Ryan Bloom" <rbb@covalent.net>
> To: <dev@apr.apache.org>; <apr-cvs@apache.org>
> Sent: Friday, August 02, 2002 7:59 PM
> Subject: RE: cvs commit: apr/poll/unix poll.c
>
>
> > >   Modified:    poll/unix poll.c
> > >   Log:
> > >     We safely ignore palloc failures [we can segv in the allocator].
> > >     We cannot ignore alloca/malloc failures.
> >
> > We generally ignore memory allocation errors of all kinds in the server
> > and APR.  The general thought has always been that if you are actually
> > running out of memory or stack space, then your computer is hosed
> > anyway, and you are going to seg fault.  Why can't we follow the same
> > rules here?
> >
> > Ryan
> >
> >
> >
>
>