On Sunday, 10 March 2013 at 11:58:39 UTC, Druzhinin Alexandr
wrote:
On 10.03.2013 18:11, simendsjo wrote:
On Sunday, 10 March 2013 at 11:06:41 UTC, simendsjo wrote:
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.
Ah, nevermind. Just found "callgrind"..
Why are you pretty sure? The difference is garbage collector
only that scans memory and causes wrong read from valgrind POV
and mangling makes work with it harder a little bit. But
profiling, heap usage and memory leaks are the same I'm sure .
I use it recently but I found one bug and it was simple and
clear - I mean bug finding.
My "pretty sure" was referring to the fact that the callgraph
only printed the function I was looking at. As I said,
"--tool=callgrind" was the option I was looking for.
