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 -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
