Package: valgrind Version: 1:3.2.3-1 Severity: minor The valgrind manpage says that --undef-value-errors defaults to yes, and that setting it to yes causes memcheck to not detect undefined value errors. I think that it means that setting it to *no* causes this behavior.
Daniel -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages valgrind depends on: ii libc6 2.6.1-1 GNU C Library: Shared libraries Versions of packages valgrind recommends: ii gdb 6.6.dfsg-1 The GNU Debugger -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
