Hey DM,
I was playing with a new setup today, and found a coredump file.
I would have been setting up the system - so its quite possible it occurred while tweaking config params - but I didnt notice that it occurred and thus what I was doing when it did.
Its not a debug version - but maybe there is enough in the backtrace?
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/opt/sbbs/exec/sbbs -syslog'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. [Current thread is 1 (Thread 0x7f252bfff700 (LWP 816))]
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007f2565e2142a in __GI_abort () at abort.c:89
#2 0x00007f2565e5dc00 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f2565f52fd0 "*** Error in `%s': %s: 0x%s ***\n")
at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007f2565e63fc6 in malloc_printerr (action=3, str=0x7f2565f53098 "double free or corruption (out)", ptr=<optimized out>, ar_ptr=<optimized out>)
at malloc.c:5049
#4 0x00007f2565e6480e in _int_free (av=0x7f2566186b00 <main_arena>, p=0x7f251c4dd4e0, have_lock=0) at malloc.c:3905
#5 0x00007f25677e6aec in msgQueueFree () from /opt/sbbs/exec/libsbbs.so
#6 0x00007f25677e6b80 in msgQueueDetach () from /opt/sbbs/exec/libsbbs.so
Sysop: | BrokenMind |
---|---|
Location: | Central Pennsylvania United States |
Users: | 60 |
Nodes: | 4 (0 / 4) |
Uptime: | 17:28:13 |
Calls: | 175 |
Files: | 2,017 |
Messages: | 20,380 |