1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • segfault in mqtt_client_on

    From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Wed Aug 7 21:29:52 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/768#note_5462

    The `node` (pointer) value here (`0xb10e9025526b2b45`) does look sus.

    The questions (to myself) are:
    - was the client_list successfully locked? Should've been looking at the code. - was the client_list corrupted? Appears that way. Not clear how that happened. --- SBBSecho 3.20-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 Aug 7 21:57:54 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/768#note_5463

    I couldn't tell you. I've updated and recompiled since then and deleted the core since it had been around for a few days.
    --- SBBSecho 3.20-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 Aug 7 22:55:44 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/768#note_5464

    Right, those are just unanswered questions (to myself), not really for you to answer.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Tue Aug 13 22:56:40 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/768#note_5528

    One possibility is that I updated my system along with mqtt and restarted sbbs but since it would have been compiled against a different library then that could have caused the fault. I think I saw something similar some time ago. Would that make sense?
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)