Crashes with SIGILL on startup

[Albrecht Dreß]

Binary package hint: valgrind

Machine: Powermac G4 "Silver", PowerPC 7450/800
System: Lucid beta

Valgrind crashes immediately on startup. Running in gdb gives the following information:

albrecht@antares:~$ gdb /usr/bin/valgrind.bin
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/valgrind.bin...done.
(gdb) run
Starting program: /usr/bin/valgrind.bin
process 2839 is executing new program: /usr/lib/valgrind/memcheck-ppc32-linux

Program received signal SIGILL, Illegal instruction.
0x380349fc in vgPlain_machine_get_hwcaps () at m_machine.c:568
568 m_machine.c: No such file or directory.
        in m_machine.c
(gdb) bt
#0 0x380349fc in vgPlain_machine_get_hwcaps () at m_machine.c:568
#1 0x38036330 in valgrind_main (argc=1, argv=0xbffff754, envp=0xbffff75c) at m_main.c:1639
#2 0x3803a178 in _start_in_C_linux (pArgc=0xbffff750) at m_main.c:2853
#3 0x38035340 in _start ()

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: valgrind 1:3.6.0~svn20100212-0ubuntu4
Uname: Linux 2.6.33.2 ppc
Architecture: powerpc
Date: Sat Apr 10 18:38:08 2010
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release powerpc (20091028)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: valgrind

[Albrecht Dreß (albrecht-dress)]

> Valgrind starts immediately on startup.

Ummm - this should read: Valgrind *crashes* immediately on startup.

[Loïc Minier (lool)]

I think the backtrace in gdb might be bogus: valgrind triggers these SIGILLs to check what your host support, but these should be catched. The SIGILL which crashes valgrind for you might be in another place.

Could you please try again in gdb but please use this command first:
handle SIGILL nostop

[Alessandro Ghedini (ghedo)]

This should have been already fixed.