Open GoogleCodeExporter opened 9 years ago
The crash in the allocator is fixed in r139, serf_bucket_mem_[c]alloc now
return NULL when no memory could be allocated from the pool.
However, nowhere in serf do we check for pointer nullness. The proposed
solution is to add a callback function that - if defined by the application -
is called when no memory can be allocated (// apr_abortfunc_t).
Original comment by lieven.govaerts@gmail.com
on 21 Jun 2010 at 12:09
Original issue reported on code.google.com by
lieven.govaerts@gmail.com
on 10 Jun 2010 at 1:27