Hello There,
I noticed recently that that I can run Echocfg ok but when Echocfg exits it gives a response of:
-------------------------------------
sbbs@bbs5:~/exec$ ./echocfg
Synchronet FidoNet Configuration Version 3.06 Copyright 2019 Rob Swindell
echocfg: ../../src/xcb_io.c:239: poll_for_event: Assertion `dpy->xcb->event_owner == XlibOwnsEventQueue && !dpy->xcb->event_waiter' failed.
Aborted (core dumped)
-------------------------------------
If I load Echocfg and immediately exit I get a response of: -------------------------------------
sbbs@bbs5:~/exec$ ./echocfg
Synchronet FidoNet Configuration Version 3.06 Copyright 2019 Rob Swindell
Segmentation fault (core dumped)
-------------------------------------
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.
Hello Digital Man,line.
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"
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 76:09:00 |
Calls: | 6,489 |
Calls today: | 2 |
Files: | 12,096 |
Messages: | 5,276,210 |