Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

sbbsecho segmentation fault

8 views
Skip to first unread message

Dumas Walker

unread,
Feb 16, 2024, 10:34:45 AM2/16/24
to
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.

#

---
ş Synchronet ş CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
--- Synchronet 3.20a-Linux NewsLink 1.114
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

Digital Man

unread,
Feb 16, 2024, 1:50:41 PM2/16/24
to
To: Dumas Walker
Re: sbbsecho segmentation fault
By: Dumas Walker to All on Fri Feb 16 2024 10:28 am

> 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.

If you could provide a backtrace, that'd allow us to help you root-cause and likely work-around the issue:
https://wiki.synchro.net/howto:gdb
--
digital man (rob)

This Is Spinal Tap quote #22:
David St. Hubbins: Here lies David St. Hubbins... and why not?
Norco, CA WX: 58.9øF, 75.0% humidity, 3 mph SSW wind, 0.00 inches rain/24hrs

Dumas Walker

unread,
Feb 17, 2024, 10:53:06 AM2/17/24
to
To: DIGITAL MAN
> > 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?


* SLMR 2.1a * Must Go - Some Jehovahs witnesses need shouting at.

---
ş Synchronet ş CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Digital Man

unread,
Feb 17, 2024, 10:55:07 PM2/17/24
to
To: Dumas Walker
Re: sbbsecho segmentation fau
By: Dumas Walker to DIGITAL MAN on Sat Feb 17 2024 10:50 am

> > > 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.
--
digital man (rob)

Breaking Bad quote #51:
I did it for me. I liked it. I was good at it. And.. I was really.. I was alive
Norco, CA WX: 53.5øF, 82.0% humidity, 7 mph W wind, 0.00 inches rain/24hrs

Dumas Walker

unread,
Feb 18, 2024, 3:06:45 PM2/18/24
to
To: DIGITAL MAN
> Check your src/build/localdefs.mk file.

Thanks. Commented out a line and that did it.

(gdb) thread apply all bt

Thread 1 (Thread 0x7ffff76b8740 (LWP 1025490) "sbbsecho"):
#0 0x0000555555574799 in main (argc=2, argv=0x7fffffffe4c8) at sbbsecho.c:6439


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.


* SLMR 2.1a * Look maw, kitty goes POP when ya plug er in da waal.

---
þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Digital Man

unread,
Feb 18, 2024, 3:51:22 PM2/18/24
to
To: Dumas Walker
Re: sbbsecho segmentation fau
By: Dumas Walker to DIGITAL MAN on Sun Feb 18 2024 11:20 am

> 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
--
digital man (rob)

This Is Spinal Tap quote #23:
David St. Hubbins: I envy us.
Norco, CA WX: 63.8øF, 61.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs

Dumas Walker

unread,
Feb 19, 2024, 3:06:44 PM2/19/24
to
To: DIGITAL MAN
> > 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

Good to know. I will be upgrading the test system soon and should pick up
that fix. Thanks.


* SLMR 2.1a * About as useful as a chocolate teapot.

---
ţ Synchronet ţ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
0 new messages