How to debug long-lived D program memory usage?
Adam D. Ruppe
destructionator at gmail.com
Wed Apr 17 22:37:38 UTC 2019
On Wednesday, 17 April 2019 at 19:07:46 UTC, Jacob Carlborg wrote:
> Perhaps try some of these flags [1] and [2].
oooh, those are very interesting too.
What I was kinda hoping is it would have stats for which file and
line of code was responsible for most allocations; a detailed
profile. But even so, this is an interesting gem.
> There's no documentation and there's no generic `--DRT-help`
> flag. It's a mess.
Indeed, we need to fix that. But I'm too lazy to do it myself :(
More information about the Digitalmars-d-learn
mailing list