I am getting a segmentation fault when trying to run synchronet 3.19 on a new system.
./sbbsecho -in
SBBSecho v3.14-Linux (master/cb76b1463) - Synchronet FidoNet EchoMail Tosser
Loading configuration files from /home/bbs/ctrl/
SBBSecho 3.14-Linux master/cb76b1463 Feb 20 2022 GCC 7.5.0 (PID 653114) invoked with options: -in
Configured: 7 archivers, 8 linked-nodes, 12 echolists
NetMail directory: /home/bbs/netmail/
Secure Inbound directory: /home/bbs/fido/inbound/
Non-secure Inbound directory: /home/bbs/fido/in/
Outbound (BSO root) directory: /home/bbs/fido/out/
Reading /home/bbs/data/AREAS.BBS
COOKING: Unrecognized internal code, assumed passthru
FIDOTEST: Unrecognized internal code, assumed passthru
FSX_TST: Unrecognized internal code, assumed passthru
LOCALTST: Unrecognized internal code, assumed passthru
BADAREA: Unrecognized internal code, assumed passthru
Read 7 areas from /home/bbs/data/AREAS.BBS
Segmentation fault
Why am I trying to run 3.19? So I can upgrade it to 3.20, and test out some other stuff I want to try, without messing my "real" board up. Thanks.
Read 7 areas from /home/bbs/data/AREAS.BBS
Segmentation fault
Why am I trying to run 3.19? So I can upgrade it to 3.20, and test out som
other stuff I want to try, without messing my "real" board up. Thanks.
If you could provide a backtrace, that'd allow us to help you root-cause and l
ely work-around the issue:
https://wiki.synchro.net/howto:gdb
Read 7 areas from /home/bbs/data/AREAS.BBS
Segmentation fault
Why am I trying to run 3.19? So I can upgrade it to 3.20, and test out som
other stuff I want to try, without messing my "real" board up. Thanks.
If you could provide a backtrace, that'd allow us to help you root-cause and l
ely work-around the issue:
https://wiki.synchro.net/howto:gdb
Thanks. However, I already tried part of this. That is to say, I did the following as per some instructions on the wiki page:
#:~/repo/src/sbbs3$ SBBSEXEC=/sbbs/exec make symlinks DEBUG=1 /home/bbs/repo/src/sbbs3/../build/Common.gmake:132: *** Both DEBUG and RELEASE are defined. Stop.
So, for fun, I then tried it without symlinks:
#:~/repo/src/sbbs3$ SBBSEXEC=/sbbs/exec make DEBUG=1 /home/bbs/repo/src/sbbs3/../build/Common.gmake:132: *** Both DEBUG and RELEASE are defined. Stop.
As I do not have RELEASE=1 on the make command line, why does it think I am trying to compile DEBUG *and* RELEASE, and how do I tell it I am not?
Check your src/build/localdefs.mk file.
Line 6439 deals with the BADAREA. Looks like it didn't like this entry in AREAS.BBS:
BADAREA *
so I removed it and sbbsecho is working now.
Line 6439 deals with the BADAREA. Looks like it didn't like this entry in AREAS.BBS:
BADAREA *
so I removed it and sbbsecho is working now.
Okay, good. Looks like that bug was fixed already for v3.20: https://gitlab.synchro.net/main/sbbs/-/commit/2962e4a5bf733e4b0c3869c43daebc5
Sysop: | SBDSTech |
---|---|
Location: | Los Angeles, CA |
Users: | 6 |
Nodes: | 15 (0 / 15) |
Uptime: | 14:18:54 |
Calls: | 185 |
Files: | 841 |
Messages: | 22,356 |