[Bug malloc/32996] malloc regression on i686

[dj at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=32996

dj at redhat dot com <dj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dj at redhat dot com

--- Comment #8 from dj at redhat dot com <dj at redhat dot com> ---
I've been debugging this for a couple of days, my findings so far... 

something is corrupting Qt's memory (i.e. the heap), I think, although I don't
know who yet.  It ends up calling free() with a pointer that was never returned
by any malloc API.  That pointer points to the word before the next chunk, and
that word is all zeros, but probably because it's the last word of an in-use
chunk (the next word is 0x61, which has the PREV_CHUNK_INUSE bit set, and
corresponds to chunks passed by the malloc API)

Unfortunately, I've found that the use of any interposer makes the problem "go
away" - so no tracer, or valgrind, etc.  That means I've annotated my copy of
malloc.c with a ton of write() calls to debug this ;-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.