Dan,
The log.txt attached to the bug report shows that you're running under gdb
and gdb is getting a SIGSEGV, halting you in sig_compute_pc_index().
This is perfectly normal, as gtk-gnutella is triggering a SIGSEGV on purpose,
and trapping it, in order to compute where the current PC is stored in the
signal context, dynamically.
Under gdb, you simply need to hit "cont" to resume execution at that point.
Note that you should not run gtk-gnutella under gdb without taking care of
some specific setup, like for instance:
ha SIGPIPE noprint nostop pass
or you're going to get seriously annoyed by all these SIGPIPE you'll get.
Cheers,
Raphael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
