1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • sbbsctrl.exe APPCRASH

    From Digital Man@1:103/705 to Codefenix on Sat Mar 11 14:53:58 2023
    Re: sbbsctrl.exe APPCRASH
    By: Codefenix to Digital Man on Sat Mar 11 2023 05:39 pm

    DM, if you'd like, I can send you both my good and bad file.ini for comparison.

    Yes, please!
    --
    digital man (rob)

    Breaking Bad quote #33:
    This guy [Gale], it's like scarface had sex with Mr. Rogers. - Hank Schrader Norco, CA WX: 63.5øF, 91.0% humidity, 6 mph SSE wind, 0.37 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Codefenix@1:103/705 to Digital Man on Sat Mar 11 18:43:56 2023
    Re: sbbsctrl.exe APPCRASH
    By: Digital Man to Codefenix on Sat Mar 11 2023 02:53 pm

    Yes, please!

    Sent.

    |01<|09co|03d|11e|15Ÿ|11e|03n|09ix|01>|07
    ---
    þ Synchronet þ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Codefenix on Sat Mar 11 18:54:46 2023
    Re: sbbsctrl.exe APPCRASH
    By: Codefenix to Digital Man on Sat Mar 11 2023 06:43 pm

    Re: sbbsctrl.exe APPCRASH
    By: Digital Man to Codefenix on Sat Mar 11 2023 02:53 pm

    Yes, please!

    Sent.

    Thank you!

    I narrowed it down (quickly) to the min_dspace setting. Yours was set to 16384P (petabytes), which exceeds the value that can be stored in a 64-bit (signed) integer and that appears to do something weird when called that code was called from sbbsctrl.exe that caused all subsequent floating point operations to cause a "invalid operation" floating point exception. I added some code to force that value within the range of a 64-bit integer, but it's still kind of mysterious why that happens, and only with sbbsctrl.exe.

    Did you intentionally change the min disk space setting to that (very high) value or is that also a mystery? :-)
    --
    digital man (rob)

    Rush quote #47:
    All of us get lost in the darkness, dreamers learn to steer by the stars
    Norco, CA WX: 57.5øF, 96.0% humidity, 2 mph E wind, 0.07 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Codefenix@1:103/705 to Digital Man on Sun Mar 12 13:42:00 2023
    Re: sbbsctrl.exe APPCRASH
    By: Digital Man to Codefenix on Sat Mar 11 2023 06:54 pm

    I narrowed it down (quickly) to the min_dspace setting. Yours was set to 16384P (petabytes), which exceeds the value that can be stored in a 64-bit (signed) integer and that appears to do something weird when called that code was called from sbbsctrl.exe that caused all subsequent floating point operations to cause a "invalid operation" floating point exception. I added some code to force that value within the range of a 64-bit integer, but it's still kind of mysterious why that happens, and only with sbbsctrl.exe.

    Awesome!

    Yeah, I noticed the 16384P as well and wondered if that had something to do with the problem.

    Did you intentionally change the min disk space setting to that (very high) value or is that also a mystery? :-)

    No, I have no idea how it got set that high. Definitely didn't change that value intentionally.

    Any chance that it could have gotten changed between iterations of 3.20a? If
    I missed a jsexec update between builds, could that cause a corrupted ini?

    |01<|09co|03d|11e|15Ÿ|11e|03n|09ix|01>|07
    ---
    þ Synchronet þ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Codefenix on Sun Mar 12 14:09:32 2023
    Re: sbbsctrl.exe APPCRASH
    By: Codefenix to Digital Man on Sun Mar 12 2023 01:42 pm

    Yeah, I noticed the 16384P as well and wondered if that had something to do with the problem.

    Did you intentionally change the min disk space setting to that (very high) value or is that also a mystery? :-)

    No, I have no idea how it got set that high. Definitely didn't change that value intentionally.

    Any chance that it could have gotten changed between iterations of 3.20a? If
    I missed a jsexec update between builds, could that cause a corrupted ini?

    I think at some point during the v3.20a dev I did change that value from kilobytes to bytes and that might have triggered something to change that value. I'll experiment and see what I can find.
    --
    digital man (rob)

    Sling Blade quote #22:
    Karl: I don't reckon you have to go with women to be a good father to a boy. Norco, CA WX: 63.4øF, 74.0% humidity, 10 mph S wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)