https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #13 from Joshua Nelson ---
Created attachment 135919
--> https://bugs.kde.org/attachment.cgi?id=135919=edit
strace of `rustc --version` (without going through the shim)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #12 from Joshua Nelson ---
Milian,
The default rustc in path is just a shim, it's not important. Rustup uses it to
switch between the stable and nightly compilers. Heaptrack can run on it fine,
because it's only tracking the shim
https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #10 from Joshua Nelson ---
Hi Milian, is there anything more I can do to help debug this? Happy to collect
more info if you think it would be useful.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #9 from Joshua Nelson ---
(In reply to Milian Wolff from comment #8)
> I see, interesting. is the shim doing anything special? maybe it's handling
> of execve/fork is messing up something in heaptrack. anyhow, a proper
>
https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #7 from Joshua Nelson ---
Right - `heaptrack` is just tracking the rustup shim for rustc, which is
not very helpful. It doesn't include any info about the compiler itself.
On Thu, Jan 21, 2021 at 2:09 PM Dániel Buga
wrote:
> ht
https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #5 from Joshua Nelson ---
Millian, thanks for getting back. Unfortunately, heaptrack has absolutely no
output on the Rust compiler. I confirmed it has logging for other programs:
```
> bin/heaptrack lsheaptrack output will be writ
