Your message dated Sun, 25 Nov 2012 16:55:05 +0100 with message-id <20121125155505.GA27297@wakko> and subject line Re: Bug#266931: valgrind --trace-children=no still traces children (poorly) has caused the Debian Bug report #266931, regarding valgrind --trace-children=no still traces children (poorly) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 266931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266931 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: valgrind Version: 1:2.1.2-2 Severity: normal valgrind --trace-children=no seems to simply include valgrind in the process that gets forked on a fork() call -- there's one "ERROR SUMMARY" per process, for example, and the behavior of "valgrind --trace-children=no --db-attach=yes" (which is equivalent to "valgrind --db-attach=yes") is totally confusing -- all the valgrind processes print independent "attach to debugger?" dialogs, with a random one getting the user's keypresses, which is almost unusable. You can see this if you debug this program with "valgrind --db-attach=yes": --- #include <stdio.h> int main(int argc, char **argv) { int i, j; fork(); for(i=0; i<4; i++) printf("%d\n", j); sleep(15); } -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.7+mppe Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 Versions of packages valgrind depends on: ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an -- no debconf information
--- End Message ---
--- Begin Message ---On gio, ago 19, 2004 at 02:55:48 -0400, Andrew Moise wrote: > Package: valgrind > Version: 1:2.1.2-2 > Severity: normal > > valgrind --trace-children=no seems to simply include valgrind in the process > that gets forked on a fork() call -- there's one "ERROR SUMMARY" per process, This is the correct behaviour. The --trace-children=no is meant to avoid tracing exec()ed sub-processes. From the valgrind(1) man page: > --trace-children=<yes|no> [default: no] > When enabled, Valgrind will trace into sub-processes initiated via the > exec system call. This is necessary for multi-process programs. > > Note that Valgrind does trace into the child of a fork (it would be > difficult not to, since fork makes an identical copy of a process), so > this option is arguably badly named. However, most children of fork > calls immediately call exec anyway. Cheers -- perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
--- End Message ---
