[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9273: 23.3; malloc initialization should (sometimes) happen at runti

From: Ken Brown
Subject: bug#9273: 23.3; malloc initialization should (sometimes) happen at runtime
Date: Sat, 13 Aug 2011 10:53:25 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0

On 8/13/2011 10:41 AM, Eli Zaretskii wrote:
Date: Sat, 13 Aug 2011 09:48:52 -0400
From: Ken Brown<address@hidden>
CC: "address@hidden"<address@hidden>

_heapinfo is indeed consistent with the current heap.  But the pointer
that was passed to realloc points into the old heap.  So applying BLOCK
to that pointer yields an absurd result.  I can easily catch such cases
by testing for ptr<  _heapbase, as in my patch to _free_internal_nolock,
but I have to figure out the best way to handle them once I've caught

malloc a buffer, then copy the contents of the old one to the new
one.  You will have to know the size of the old block, which means you
will have to access the old copy of _heapinfo.

Thanks!  That's much easier than what I was trying to do.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]