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-children=yes help? I tried running `cargo build`, `cargo rustc`, and `rustc`, but I think they must all spin off children because `--trace-children=yes` seems to work! Perhaps valgrind could detect children and add a warning pointing users to this flag? Otherwise it can be quite confusing why there's no output whatsoever. In fact I guess I'm still confused why DHAT didn't produce any output for the parent process (cargo). -- You are receiving this mail because: You are watching all bug changes.
