[Bug malloc/21731] Bad malloc heuristic result in 30-40x memory consumption

["carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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

--- Comment #15 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Yichao Yu from comment #14)
> So I guess I might be able to find this info out by reading the link in the
> previous comment but is there a simple way to dump the heap map? Last time I
> check it's consistent with glibc leaving the big hole unfilled but it'll be
> nice if I can verify that.

Unfortunately we don't have a good heap dumper. DJ had a heap dump visualizer,
but we haven't developed it beyond prototype. We are open to any suggestions
about how best to handle this, but so much application specific information is
required that you need to write custom tooling to help you. The graphing octave
code I have is the most generic examples I could come up with that I use every
time I have to analyze something like this for a user.

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