https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #12 from Joshua Nelson <jyn...@gmail.com> ---
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 and not the compiler itself (the shim
spawns the compiler as a new process).
> Can you attach strace logs for running both versions, i.e. something like
> `strace -e file -e process -f`
Here's an strace for the actual compiler:
$ strace -e file -e process -f
/home/joshua/.local/lib/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc
--version
execve("/home/joshua/.local/lib/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/rustc",
["/home/joshua/.local/lib/rustup/t"..., "--version"], 0x7ffec9ecad90 /* 34 vars
*/) = 0
arch_prctl(ARCH_SET_FS, 0x7f5f5e98a4c0) = 0
rustc 1.52.0-nightly (0148b971c 2021-02-18)
exit_group(0) = ?
+++ exited with 0 +++
I'll attach a full strace with all syscalls shown in just a second.
--
You are receiving this mail because:
You are watching all bug changes.
