Hello Digital Man,

> A backtrace from that core dump might be very helpful:
> http://wiki.synchro.net/howto:gdb
> You might also try running echocfg in one of the other '-i' modes (e.g. -is)
> and see if that avoid the issues.

Ok... Here's a wierd one. I stopped the sbbs daemon. As suggested I edited the
sbbs file in /etc/init.d and uncommented the "ulimit -c unlimited" line. I then
 added the following lines to the /etc/sysctl.conf file.

# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
kernel.core_pattern = /tmp/core.%e.%p

I then restarted the sbbs daemon. I then loaded ./echocfg which loaded ok. Then
 exited echocfg and got no errors or faults. I then stopped the sbbs daemon and
 commented out the "ulimit -c unlimited" line and restarted the sbbs daemon. I
reloaded and exited ./echocfg with no errors or faults. I then stopped the
daemon again and commented out the "kernel.core_uses_pid = 1"  and
"kernel.core_pattern = /tmp/core.%e.%p" line. Then restarted the sbbs daemon
again and loaded ./echocfg once again. Upon exiting I got the following
response


sbbs@bbs5:~/exec$ ./echocfg 
---------------------------------------------------------------------------
Synchronet FidoNet Configuration  Version 3.06  Copyright 2019 Rob Swindell

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
      after 173 requests (173 known processed) with 0 events remaining.
---------------------------------------------------------------------------

I did try the various display modes and none seemed to generate and errors.


Jeff

--- BBBS/Li6 v4.10 Toy-4
 * Origin: Fidoneet: The Ouija Board - Anoka, MN -bbs.ouijabrd.net (1:282/1031)