[valgrind] [Bug 405516] Memcheck with Ruby produces numerous outputs
https://bugs.kde.org/show_bug.cgi?id=405516 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be --- Comment #3 from Philippe Waroquiers --- Looking at the trace file: As explained by Tom, when you launch ruby, several forks and at least one exec happens. Right at the beginning, you see that valgrind is reading /usr/bin/ruby and then goes on to read /usr/bin/bash. So, it looks like /usr/bin/ruby is a bash script which then launches various things via fork and some exec. Completely at the end, it does an exec of /usr/bin/ruby-mri I will assume that this is the real ruby interpreter or whatever. The conclusion: if you want to analyse what the ruby interpreter does, you have to give --trace-children=yes otherwise what you are valgrind-ing will just be the wrapper around the real ruby thing. You might eliminate some of the output by playing with --trace-children-skip=patt1,patt2,... and/or --trace-children-skip-by-arg=patt1,patt2,... and/or --child-silent-after-fork=no|yes but --trace-children=yes seems mandatory. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405516] Memcheck with Ruby produces numerous outputs
https://bugs.kde.org/show_bug.cgi?id=405516 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Tom Hughes --- Well because something is creating new threads or processes which are then exiting. That's why each exit references a different PID in the message prefixes. I'm not sure why a trivial ruby program would create extra threads but it's something you would need to ask ruby people, not us. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405516] Memcheck with Ruby produces numerous outputs
https://bugs.kde.org/show_bug.cgi?id=405516 --- Comment #1 from niko.pelko...@hotmail.com --- Created attachment 118836 --> https://bugs.kde.org/attachment.cgi?id=118836&action=edit Debug file So I ran this command to enable more debugging: valgrind --tool=memcheck -v -v -v -d -d -d --trace-syscalls=yes ruby hello.rb Here's the full output as a txt file -- You are receiving this mail because: You are watching all bug changes.
