Your message dated Wed, 8 Feb 2006 12:56:55 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#253517: your valgrind bug: valgrind seg-faults even when
running --help
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: valgrind
Version: 1:2.1.1-3
Severity: normal
valgrind seg-faults immediately every time I run it, even with a
simple program or when running --help. For example:
liberty:~/src$ valgrind ls
Segmentation fault (core dumped)
liberty:~/src$ valgrind --help
Segmentation fault (core dumped)
liberty:~/src$
I'm baffled. I tried to a stack trace on the dumped core, but it's
gibberish. (Memory locations such as 0x00000000 and 0x500000000).
If I unset VALGRIND_OPTS and run "valgrind.bin --help", that works.
"valgrind.bin --tool=memcheck" seg-faults, as does "--tool=<any valid
tool>".
The valgrind that was in testing a few months ago worked fine on the
same system.
-- System Information:
Debian Release: 3.0
APT prefers testing
APT policy: (980, 'testing'), (977, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26liberty
Locale: LANG=C, LC_CTYPE=C
Versions of packages valgrind depends on:
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
-- no debconf information
--
Daniel Stutzbach Computer Science Ph.D Student
http://www.barsoom.org/~agthorr University of Oregon
--- End Message ---
--- Begin Message ---
On Wed, Feb 08, 2006 at 03:42:11PM -0500, Justin Pryzby wrote:
> A long time ago you reported a valgrind bug to the Debian BTS:
> valgrind seg-faults even when running --help
> http://bugs.debian.org/253517
>
> Has this been resolved in recent versions of the valgrind package?
Yes, thanks!
--
Daniel Stutzbach Computer Science Ph.D Student
http://www.barsoom.org/~agthorr University of Oregon
--- End Message ---
