Details
Description
I'm tracking a memory leak in 2.0.1 (possibly exists in latest versions too) and I am relying on the freelist_dump from when a USR1 signal is sent to gather information to determine where a memory leak is happening (I lose 5G a day).
I notice that it started showing negative numbers pretty quickly when one of the lists was using more than 2G, so I looked in the code and found fprintf was using %d, considering the storage for allocated, type_size,count are unsigned 32 bit integers, that explained the zero.
I have patched my code to use unsigned and unsigned long long to avoid me losing information in these dumps.
I checked at this is still the case in at least 2.1.7.