https://bugs.kde.org/show_bug.cgi?id=405516
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
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.
