Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <000801c23a58$74555e40$7300a8c0@MITHRIL>
From: "David Reid" <dreid@jetnet.co.uk>
To: <dev@apr.apache.org>
References: <000c01c23a56$bc5e2480$3600000a@KOJ>
Subject: New poll code
Date: Fri, 2 Aug 2002 20:11:49 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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
>
>
>