1. Forum
  2. FidoNet
  3. SYNC PROGRAMMING

  • src/xpdev/threadwrap.h

    From Deucе@1:103/705 to Git commit to main/sbbs/master on Sat Feb 19 14:03:12 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/3d0d525c7da0d33b4f53547b
    Modified Files:
    src/xpdev/threadwrap.h
    Log Message:
    Use MinGW32 types for pthread_t and pthread_mutex_tuintptr_t should be the same as a DWORD on Win32,and CRITICAL_SECTION can be stored in an inptr_t as well.This should work fine, and allow more build environments to be happy.This is generally caused by new C++ standards having thread supportin the standard library, so wrappers getting pushed deeper in.At some pointer, this should be redone with standard threads, butnow is not the time.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to Git commit to main/sbbs/master on Sun Feb 20 16:53:52 2022
    https://gitlab.synchro.net/main/sbbs/-/commit/b3c536e4e065801ed59d9c42
    Modified Files:
    src/xpdev/threadwrap.h
    Log Message:
    pthread_mutex_t is a CRITICAL_SECTION (not a pointer) on Win32Partially revert Deuce's commit b4bc9c9759e6f34c272501e024This explains the EAccessViolation (stack corruption during sbbs startup) that sysops have reported when using the latest nightly builds.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)