Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 48252  |
|  Rob Swindell (on Windows 11) to Git commit to main/sbbs/master  |
|  src/sbbs3/ctrl/MainFormUnit.cpp  |
|  07 Dec 25 21:12:24  |
 TZUTC: -0800 MSGID: 53674.syncprog@1:103/705 2d9c65e2 PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 TID: SBBSecho 3.32-Linux master/a51dd4dc5 Dec 06 2025 GCC 12.2.0 BBSID: VERT CHRS: ASCII 1 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/commit/a2cd1d341bc92ee3556a8694 Modified Files: src/sbbs3/ctrl/MainFormUnit.cpp Log Message: Wrap all ClientForm->ListView->Items accesses in try/catch ... this appears to resolve the "invalid index" exceptions that could get thrown and pop-up error dialogs in SBBSCTRL-Win32 ... finally. It's a mystery how the ListMutex isn't successfully protecting the ListView (the ListView->Items->Count becomes out of sync?), but if the array index into the ListView->Item array is invalid, it must be. Pretty weird. Also, if WaitForSIngleObject() fails (to acquire the ListView mutex), popup an error dialog box. I have not observed any mutex acquisition failures. --- SBBSecho 3.32-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715 SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110 SEEN-BY: 229/134 206 317 400 426 428 470 700 705 240/1120 5832 263/1 SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219 SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124 SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35 PATH: 103/705 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]