On 11.03.2013 02:32, Dmitry Olshansky wrote:
I didn't bother to check the text dump in depth but here is one slice:
n6: 41816 (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
n1: 8208 0x540209: _D2gc3gcx4Pool10initializeMFmbZv (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x53EBEB: _D2gc3gcx3Gcx7newPoolMFmbZPS2gc3gcx4Pool (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x53C33B: _D2gc3gcx2GC12mallocNoSyncMFmkPmZPv (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x53C1F1: _D2gc3gcx2GC6mallocMFmkPmZPv (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x51CABB: gc_malloc (in /home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x51E7A6: _d_newclass (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x545123: thread_attachThis (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x5450B5: thread_init (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x53B72B: gc_init (in
/home/dmitry/Dscanner/dscanner-dmd)
n1: 8208 0x51E710: _
....
So I guess your Mr. X is D's GC that reserves about 1Mb at start.
Thanks for answer, Dmitry! My Mr.X was opengl driver - I just checked my
code that using 3rd libs without debug symbols and found who it was.
Massif shows me gc the same way as you, I just didn't show it.
What visualizer do you use?
