On 10.03.2013 19:45, Dmitry Olshansky wrote:
10-Mar-2013 15:06, simendsjo пишет:
I haven't used valgrind/cachegrind on C/C++ programs before, but I'm
pretty sure it doesn't behave as expected on D code. I found this page
to fix the mangling issue: http://wiki.dlang.org/Other_Dev_Tools, but
all callgraphs is empty.
I've used it just yesterday with great success. At least callgrind and
massif definitely work.
Dmitry, using massif I get tree like this (there are normal informative
branches too, of course):
|
->26.85% (10,364,525B) 0xD418247: ???
| ->09.86% (3,807,325B) 0x1442E08E: ???
| | ->02.99% (1,155,831B) 0x145188A6: ???
| | | ->02.99% (1,155,831B) 0x3E: ???
| | | ->02.99% (1,155,831B) 0xEB70BC7: ???
| | | ->02.99% (1,155,831B) 0x145187CE: ???
| | | ->02.99% (1,155,831B) 0x145188A6: ???
how to know who the hell is used my memory? who is Mr. '???'?
can building phobos and druntime help with it?
