https://bugs.kde.org/show_bug.cgi?id=431746
--- Comment #6 from Dániel Buga <bugad...@gmail.com> --- Simply calling heaptrack to track rustc seems to work: ``` bin/heaptrack rustc --version heaptrack output will be written to "/home/dani/heaptrack/build/heaptrack.rustc.9925.gz" starting application, this might take some time... heaptrack debug(3) [9938:9938]@0 heaptrack_malloc(0x7fd450230320, 32) heaptrack debug(3) [9938:9938]@0 acquiring lock heaptrack debug(3) [9938:9938]@0 lock acquired heaptrack debug(3) [9938:9938]@0 releasing lock heaptrack debug(1) [9938:9938]@0 heaptrack_init(/tmp/heaptrack_fifo9925) heaptrack debug(3) [9938:9938]@0 acquiring lock heaptrack debug(3) [9938:9938]@0 lock acquired heaptrack debug(1) [9938:9938]@0 initializing: /tmp/heaptrack_fifo9925 heaptrack debug(1) [9938:9938]@0 calling initBeforeCallback heaptrack debug(1) [9938:9938]@0 done calling initBeforeCallback heaptrack debug(1) [9938:9938]@0 doing once-only initialization heaptrack debug(2) [9938:9938]@0 will write to /tmp/heaptrack_fifo9925/0x3 heaptrack debug(1) [9938:9938]@0 constructing LockedData heaptrack debug(1) [9938:9939]@0 timer thread started heaptrack debug(1) [9938:9938]@0 initialization done heaptrack debug(3) [9938:9938]@0 releasing lock heaptrack debug(3) [9938:9938]@0 heaptrack_malloc(0x55a52e3ec4d0, 72704) heaptrack debug(3) [9938:9938]@0 acquiring lock heaptrack debug(3) [9938:9938]@0 lock acquired heaptrack debug(1) [9938:9938]@0 updateModuleCache() heaptrack debug(2) [9938:9938]@0 dlopen_notify_callback: x 55a52d40f000 ``` But this hangs forever: bin/heaptrack $(rustup which rustc) --version heaptrack output will be written to "/home/dani/heaptrack/build/heaptrack.rustc.10419.gz" starting application, this might take some time... rustc 1.51.0-nightly (44e3daf5e 2020-12-31) -- You are receiving this mail because: You are watching all bug changes.
