apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <bo...@rexursive.com>
Subject Re: thread pool patch again
Date Wed, 24 May 2006 23:04:25 GMT
Quoting Henry Jen <henryjen@ztune.net>:

> Another attempt with checking result of palloc/pcalloc(thanks Davi
> pointing those out).

I'm getting more and more confused with the allocator error checking...

I thought there was no point in handling allocation errors (coming  
from our own allocator) in APR/APU, because even if we do, we'll  
eventually be screwed (i.e. we have no more memory to give). Shouldn't  
we just let things segfault, like we do in other APR/APU code?

PS. It'll also get rid of the nasty goto's in this patch.


View raw message