TID: Mystic BBS 1.12 A43   
   MSGID: 3:770/100 446a650f   
   REPLY: 1157.fido-binkd@3:633/410 21816c3b   
   TZUTC: 1300   
   On 03 Jul 2019 at 02:40p, Tony Langdon pondered and said...   
       
    TL> I've been running binkd fairly successfully for 2.5 years on this   
    TL> system, and for the most part, it's been flawless.  However, on polling   
    TL> one particular uplink, I've started getting a strange error, which is   
    TL> not giving me a lot of clues.   
      
   I ran into this today.  The root cause is a use-after-free bug in   
   binkd; this bug has been present since sometime in 2001 according   
   to the git history.  Most people probably won't notice it unless   
   your system's malloc() is aggressive about poisoning memory returned   
   by free().   
      
   I've sent a pull request to fix it upstream.   
   https://github.com/pgul/binkd/pull/16   
      
   --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)   
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)   
   SEEN-BY: 1/123 57/0 90/1 103/705 153/250 154/10 203/0 220/70 221/0   
   SEEN-BY: 227/114 229/101 200 426 1014 240/5832 249/307 317 267/800   
   SEEN-BY: 280/464 5003 5555 288/100 292/854 310/31 317/3 340/1000 342/200   
   SEEN-BY: 396/45 423/120 712/848 770/0 1 100 340 772/0 1 210 500 2452/250   
   PATH: 770/100 1 280/464 229/426