[valgrind] [Bug 415159] DHAT doesn't output anything when running the rust compiler

2019-12-28 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=415159 Julian Seward changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[valgrind] [Bug 415159] DHAT doesn't output anything when running the rust compiler

2019-12-13 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=415159 --- Comment #3 from Tom Hughes --- Well yes they will all spin off children because rustc is a separate program to cargo - it's like tracing make and it not following over the exec when it runs gcc to do the actual compile. Note that --trace-children i

[valgrind] [Bug 415159] DHAT doesn't output anything when running the rust compiler

2019-12-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=415159 --- Comment #2 from skainswo...@gmail.com --- (In reply to Tom Hughes from comment #1) > That looks like you ran valgrind on cargo rather than on the compiler? or > does the compiler run as part of cargo? > > Does tracing into children with --trace-chil

[valgrind] [Bug 415159] DHAT doesn't output anything when running the rust compiler

2019-12-13 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=415159 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --