Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32540  |
|  Rob Swindell to GitLab note in main/sbbs  |
|  event thread chucked up a core dump  |
|  04 Oct 25 14:19:12  |
 TZUTC: -0700 MSGID: 58665.sync_sys@1:103/705 2d47aa79 PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 BBSID: VERT CHRS: ASCII 1 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/issues/981#note_7698 Appreciate the backtrace. Does your `ctrl/time.ini` file appear to be corrupted? Is this reproducible (e.g. still happening)? As for the crash, some NULL pointers appear in that backtrace that shouldn't be there (e.g. the `key` argument to `iniReadDateTime()` is `0x0`) which suggests either the `scfg_t` (stored in the heap) was corrupted, or the stack got corrupted during these calls to ini_file.c functions while parsing `time.ini`. Since the scfg_t element that's used for key argument isn't a pointer in the first place (it's an array of char), I can't really imagine how it'd be set to NULL even through corruption. So that kind of points to stack corruption (e.g. in functions within ini_file.c). --- SBBSecho 3.30-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757 SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114 SEEN-BY: 229/110 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 467/888 SEEN-BY: 633/267 280 384 410 414 418 420 422 2744 712/848 770/1 902/26 SEEN-BY: 5020/400 5075/35 PATH: 103/705 280/464 633/280 229/426 |
[ << oldest | < older | list | newer > | newest >> ]