Daniel, This is a grave bug indeed. Since it appears very early in the initialization process and I cannot reproduce it here obviously, I am going to need your help to spot what is going on.
Obviously, you're going to have to run it through gdb, but you need to go past the initial SIGSEGV event, which is completely expected in the sig_compute_pc_index() routine. To do that, you need to resume execution past that initial SIGSEGV. I suggesting the following to do that easily: Put a breakpoint in assertion_message(). Then run, and continue past the initial SIGSEGV. As soon as the assertion failure occurs, you'll need to backtrace the thread and post the resulting stack. Thanks, Raphael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
