Package: valgrind
Version: 1:3.6.0~svn11254+nmu1
Severity: important

Hi!

Valgrind is broken for PowerPC, just starting it without any further
command to run already causes a segmentation fault. Running it on any
executable has the same problem.

There is a patch available, the simple recipe mentioned in
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/484048 or
http://bugs.kde.org/show_bug.cgi?id=214223 works. Or maybe one should
say it works around the issue, which could be nonportable valgrind code
or a GCC bug.

Note: This is not related to http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=529016, which also reports breakage on PowerPC,
but the problem is a different one. With the change mentioned above,
valgrind is again usable on PowerPC.

Thanks!

Uli




-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.33-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages valgrind depends on:
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib
ii  libc6-dbg                     2.11.2-7   Embedded GNU C Library: detached d

Versions of packages valgrind recommends:
ii  gdb                           7.0.1-2+b1 The GNU Debugger

Versions of packages valgrind suggests:
pn  alleyoop                      <none>     (no description available)
pn  kcachegrind                   <none>     (no description available)
pn  valkyrie                      <none>     (no description available)




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to