March 12, 2013 Re: valgrind | ||||
---|---|---|---|---|
| ||||
Posted in reply to Dmitry Olshansky | On 12.03.2013 01:28, Dmitry Olshansky wrote:
>> 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?
>
> I think it's deceptively called massif-visualizer :)
>
very, very amazing and so unexpected! :)
|
March 12, 2013 Re: valgrind | ||||
---|---|---|---|---|
| ||||
Posted in reply to Brian Schott | On 12.03.2013 01:39, Brian Schott 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.
>
> If you're on Linux I'd recommend that you also look at Perf[1], as
> Valgrind is sometimes wrong about where your code is slow.
>
> [1] https://perf.wiki.kernel.org/index.php/Tutorial
Thanks for link!
|
Copyright © 1999-2021 by the D Language Foundation