threads and contexts and allocations and frees
rra at stanford.edu
Wed Apr 17 17:38:02 EDT 2013
Greg Hudson <ghudson at MIT.EDU> writes:
> On 04/17/2013 04:49 PM, Russ Allbery wrote:
>> IIRC, this sort of thing can cause problems on Windows due to the way
>> that the allocators work (although possibly doesn't at the moment
>> depending on how the code is structured).
> On Windows, you want malloc() and free() calls to be made from the same
> compiled code unit, because the allocator memory layout depends on
> compilation flags (as I understand it). But that's not what "this sort
> of thing" is. I don't think Chris Hecker is proposing to mix
> library-malloc with application-free or vice versa.
I had vaguely remembered that Windows might use separate per-thread malloc
arenas in some situations, but some brief searching and research shows
that I probably made that up. Apologies for the noise.
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the krbdev