apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sander Striker <stri...@apache.org>
Subject Re: apr_pcalloc resulting in segfault
Date Thu, 31 Mar 2005 17:37:18 GMT
Ryan Bloom wrote:
> On Thu, 31 Mar 2005 15:37:21 +0200, Sander Striker <s.striker@striker.nl> wrote:

[...]
>>Given that, we could even opt for removing the abort callback function
>>altogether.
> 
> 
> No, we couldn't opt for removing the abort callback.  The reason that
> was added, is that it isn't valid for a library to seg fault or just
> abort in most situations.  The abort callback was added because HTTPd
> wanted to just kill the child process ASAP.  Other applications may
> want to try to print an error message in this case, so that the user
> or developer can try to figure out what went wrong.
> 
> We can't gaurantee that the app will survive the call to abort, but we
> need to at least attempt to give other applications the chance to
> behave differently from HTTPd.

I wasn't even thinking about httpd.  It all boils down to the "We can't
guarantee...".  What's the point in having it then?  Not that we can
change it at this stage, so I'll shut up now :).


Sander

Mime
View raw message