Package: valgrind
Version: 1:3.2.1-1
Severity: normal
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-etchnhalf.1-686-bigmem
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages valgrind depends on:
ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries
Versions of packages valgrind recommends:
ii gdb 6.4.90.dfsg-1 The GNU Debugger
-- no debconf information
Valgrind still returns with an exit code of zero when the following
program is run despite being called as "valgrind --error-exitcode=42".
The valgrind output also continues even after the shell prompt
returns.
I've reproduced this on etch using valgrind-3.2.1-1 and a backported
valgrind-3.3.1-2 from lenny. Occasionally valgrind behaves correctly
but most of the time it does not.
If I compile the original release valgrind-3.3.1 tarball myself then
it does not show either symptom.
I have no reason to believe that this problem is boost-specific. It
was just the easiest way for me to produce a minimal test case.
#include <boost/thread.hpp>
void CrashThread()
{
int *foo = reinterpret_cast<int *>(3);
*foo = 42;
}
int main()
{
boost::thread thread(CrashThread);
thread.join();
return 0;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
