This should have been already fixed.
** Changed in: valgrind (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/560140
Title:
Crashes with SIGILL on startup
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43698994/Dependencies.txt
--
Crashes with SIGILL on startup
https://bugs.launchpad.net/bugs/560140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Valgrind starts immediately on startup.
Ummm - this should read: Valgrind *crashes* immediately on startup.
--
Crashes with SIGILL on startup
https://bugs.launchpad.net/bugs/560140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
Binary package hint: valgrind
Machine: Powermac G4 Silver, PowerPC 7450/800
System: Lucid beta
- Valgrind starts immediately on startup. Running in gdb gives the
+ Valgrind crashes immediately on startup. Running in gdb gives the
following information:
-
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
