1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • coredump in chksmb

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Wed Mar 24 12:42:12 2021
    open https://gitlab.synchro.net/main/sbbs/-/issues/241

    Checking an echo base I received an error and then a coredump...95% 135 #136 (000000) 2nd Pass Misordered message number96% 136 #137 (000000) 2nd Pass Misordered message number97% 137 #138 (000000) 2nd Pass Misordered message number100%free(): invalid next size (normal)Aborted (core dumped)Reading symbols from /sbbs/exec/chksmb...[New LWP 1489311]Core was generated by `chksmb -e -p adventurenet/av_advbbsad'.Program terminated with signal SIGABRT, Aborted.#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:5050 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.(gdb) bt#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50#1 0x00007f9d395db859 in __GI_abort () at abort.c:79#2 0x00007f9d396463ee in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f9d39770285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155#3 0x00007f9d3964e47c in malloc_printerr (str=str@entry=0x7f9d397726b8 "free(): invalid next size (normal)") at malloc.c:5347#4 0x00007f9d3964ffbc in _int_free (av=0x7f9d397a1b80 <main_arena>, p=0x55c93084a5b0, have_lock=<optimized out>) at malloc.c:4322#5 0x000055c930537178 in main (argc=4, argv=0x7ffc54adb078) at chksmb.c:886
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Mar 24 17:26:39 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/241#note_1766

    This is in the new_file_base branch? When submitting issues, if the problem isn't with the master branch, please state which branch was in use.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Mar 24 17:36:47 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/241#note_1768

    If you could send me the msgbase (or filebase?) files that is causing this issue, that'd be helpful.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Wed Mar 24 17:38:12 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/241#note_1769

    Sorry, my bad. Yes, with the new_file_base. I'll go ahead and upload the msgfile to vert.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Mar 24 17:51:01 2021
    https://gitlab.synchro.net/main/sbbs/-/issues/241#note_1770

    Thanks for uploading the msgbase files. Unfortunately, chksmb here reports no problem with it:```CHKSMB v3.19-Win32 3.00/new_file_base SMBLIB aa3173e7d - Check Synchronet Message BaseChecking e:\nelgin\av_advbbsad Headers100%Checking e:\nelgin\av_advbbsad Data Blocks100%Checking e:\nelgin\av_advbbsad Index100%Checking e:\nelgin\av_advbbsad Hashes100%Status Total (=): 141Total Indexes (=): 141Active Indexes (=): 141Active Headers (=): 141Active Header Blocks ( ): 282 72,192 bytes usedActive Data Blocks ( ): 2545 651,520 bytes usedHeader Records ( ): 141Deleted Indexes ( ): 0Deleted Headers ( ): 0Deleted Header Blocks ( ): 0 0 bytes usedDeleted Data Blocks ( ): 0 0 bytes usedOldest Message (import) ( ): 1017 days (0 max)Largest Message (data) ( ): 10662 bytes (#62)e:\nelgin\av_advbbsad Message Base is OK```Did you maybe run something to fix the base after the chksmb failure?Do you have a backup of the corrupted base still?
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Wed Mar 24 22:11:32 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/241
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)