New poll code

[David Reid <dr...@jetnet.co.uk>]

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" <rb...@covalent.net>
To: <de...@apr.apache.org>; <ap...@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
>
>
>

RE: New poll code

[Ryan Bloom <rb...@covalent.net>]

Where can I get access to a machine that is displaying this behavior?

Ryan


----------------------------------------------
Ryan Bloom
rbb@covalent.net           rbb@apache.org

> -----Original Message-----
> From: David Reid [mailto:dreid@jetnet.co.uk]
> Sent: Friday, August 02, 2002 12: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" <rb...@covalent.net>
> To: <de...@apr.apache.org>; <ap...@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
> >
> >
> >

RE: New poll code

[Rob Saccoccio <ro...@fastcgi.com>]

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" <rb...@covalent.net>
> To: <de...@apr.apache.org>; <ap...@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
> >
> >
> >
>
>