1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • sbbsecho segmentation fault

    From Dumas Walker@CAPCITY2 to All on Fri Feb 16 10:28:53 2024
    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
  • From Digital Man to Dumas Walker on Fri Feb 16 10:50:35 2024
    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
  • From Dumas Walker@CAPCITY2 to DIGITAL MAN on Sat Feb 17 10:50:00 2024
    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
  • From Digital Man to Dumas Walker on Sat Feb 17 19:55:01 2024
    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
  • From Dumas Walker@CAPCITY2 to DIGITAL MAN on Sun Feb 18 11:20:00 2024
    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
  • From Digital Man to Dumas Walker on Sun Feb 18 12:51:16 2024
    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
  • From Dumas Walker@CAPCITY2 to DIGITAL MAN on Mon Feb 19 09:16:00 2024
    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