Your message dated Tue, 17 Jun 2008 09:59:41 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug
has caused the Debian Bug report #179452,
regarding valgrind segv's at startup on machines without RDTSC
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.)
--
179452: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=179452
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: valgrind
Version: 1.0.4-2.1
Severity: grave
Justification: renders package unusable
valgrind seems to always SEGV at startup. It can't even run
/bin/true.
[EMAIL PROTECTED] ~% valgrind /bin/true
==22090== valgrind-1.0.4, a memory error detector for x86 GNU/Linux.
==22090== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
zsh: segmentation fault valgrind /bin/true
>From the description this seems to be a different bug to #166514 (it's
not related to sockets) or #173918 (I don't see that error message).
sh -x on the valgrind wrapper shows that it is running
this command
VG_ARGS='--suppressions=/usr/lib/valgrind/woody.supp'
LD_LIBRARY_PATH=/usr/lib/valgrind LD_PRELOAD=/usr/lib/valgrind/valgrind.so
/bin/true
Because of valgrind's preload tricks I cannot at the moment get
meaningful information out of gdb.
strace shows these calls leading up to the failure:
rt_sigaction(SIGRT_13, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_14, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_15, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_16, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_17, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_18, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_19, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_20, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_21, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_22, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_23, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_24, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_25, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_26, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_27, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_28, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_29, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_30, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGRT_31, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(64, {SIG_IGN}, {SIG_IGN}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
valgrind --help works OK.
Basically any other option that I tried fails in the same way.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux toey 2.4.20 #66 Mon Dec 30 19:11:14 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages valgrind depends on:
ii libc6 2.3.1-10 GNU C Library: Shared libraries an
-- no debconf information
--
Martin
--- End Message ---
--- Begin Message ---
No feedback from this bug has been received with newer versions
--- End Message ---
