It just now occurred to me that I can install some *-dbg packages to get debugging symbols.

Here are the backtraces from two recent core dumps:

Program terminated with signal 6, Aborted.
(gdb) bt
#0  0xb7dd7556 in raise () from /lib/libc.so.6
#1  0xb7dd8d78 in abort () from /lib/libc.so.6
#2  0xb7e11aa5 in __libc_message () from /lib/libc.so.6
#3  0xb7e17845 in malloc_printerr () from /lib/libc.so.6
#4  0xb7e1a2bc in _int_malloc () from /lib/libc.so.6
#5  0xb7e1b586 in malloc () from /lib/libc.so.6
#6  0xb7f01e2b in membuffer_set_size (m=0x819836c, new_length=6)
    at src/genlib/util/membuffer.c:230
#7 0xb7f0201d in membuffer_assign (m=0x819836c, buf=0xb2400ae0, buf_len=6)
    at src/genlib/util/membuffer.c:329
#8  0xb7f037a8 in parser_parse_headers (parser=0xb2400950)
    at src/genlib/net/http/httpparser.c:1697
#9  0xb7f03b66 in parser_parse (parser=0xb2400950)
    at src/genlib/net/http/httpparser.c:2324
#10 0xb7efdbf8 in ssdp_event_handler_thread (the_data=0xb2400950)
    at src/ssdp/ssdp_server.c:690
#11 0xb7ef671c in WorkerThread (arg=0xb7f137c4) at src/ThreadPool.c:573
#12 0xb7d9af3b in start_thread () from /lib/libpthread.so.0
#13 0xb7e77bee in clone () from /lib/libc.so.6

(This is the same backtrace I reported earlier, without symbols.)

Program terminated with signal 11, Segmentation fault.
(gdb) bt
#0  0xb7e878f7 in malloc_consolidate () from /lib/libc.so.6
#1  0xb7e899a5 in _int_malloc () from /lib/libc.so.6
#2  0xb7e8b299 in calloc () from /lib/libc.so.6
#3  0xb7e801ed in open_memstream () from /lib/libc.so.6
#4  0xb7ee40f8 in __vsyslog_chk () from /lib/libc.so.6
#5  0xb7ee4647 in vsyslog () from /lib/libc.so.6
#6  0x0804c84f in trace (debuglevel=2,
    format=0x804dbb0 "ExpireMapping: Proto:%s Port:%s\n") at util.c:70
#7  0x0804a390 in ExpireMapping (input=0x85354d8) at gatedevice.c:782
#8  0xb7f6671c in WorkerThread (arg=0x80504e0) at src/ThreadPool.c:573
#9  0xb7e0af3b in start_thread () from /lib/libpthread.so.0
#10 0xb7ee7bee in clone () from /lib/libc.so.6

(This is a new backtrace from a more recent crash.)

Looks like some kind of memory corruption, perhaps... I'll do a bit more investigation and report more if I discover anything further.

--
Rob Leslie
r...@mars.org




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to