On Mon, Dec 01, 2008 at 12:48:35PM -0800, Arun Sharma wrote:
On Mon, Dec 1, 2008 at 12:43 PM, Bob Bell <[EMAIL PROTECTED]>wrote:
> The systems where I use libunwind have relatively small stacks. Parts
> of libunwind put PATH_MAX on the stack, sometimes more than once. This
> can lead to stack overflow, at which point my applications die without
> *ANY* indication of why they died.
>
> I'm using the patch below. It converts the big stack allocations I've
> found into mallocs. It remedies the problems I've been seeing, at least
> for me.
Please do not introduce mallocs in libunwind. It makes libunwind unusable as
a heap profiler.
Does mempool_alloc() work for you?
I almost added a disclaimer about not knowing if malloc() was
"permitted", but didn't. I will attempt to use mempool_alloc() instead
and report back my results.
--
Bob Bell
_______________________________________________
Libunwind-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/libunwind-devel
