Subj : Re: Compiling from source
To   : Avon
From : tenser
Date : Wed Jan 27 2021 02:59:47

On 26 Jan 2021 at 09:21p, Avon pondered and said...
 
 Av> [snip]
 Av> 
 Av> Spoon did try to post the packet, NNTP (rightfully) said No.
 Av> 
 Av> Posting news to xxx.xxx.xxx.xxx
 Av> * Posting article to nz.test
 Av> NNTP host returned error: 441 435 Duplicate
 Av> ! NNTP server did not accept message
 Av> free(): double free detected in tcache 2
 Av> Aborted

Sorry, I haven't been keeping up here, but this is a bug
in that software: the code is simply mismanaging memory.
The solution here is to find the bug and fix it; sadly,
much of this stuff is an unmaintained mess....  But trying
a 32-bit build won't fix it, as was suggested earlier.

 Av> Despite the failed post Spoon is not exiting correctly. This has been the
 Av> same error I have seen in all my test compiles. 
 Av> 
 Av> free(): double free detected in tcache 2
 Av> Aborted
 Av> 
 Av> Not sure what that is or how to fix, but I can report when Soupgate
 Av> creates an exported message it generates a number of .MSG files holding
 Av> the gated posts to be sent to the NNTP and a REPLIES file that acts like
 Av> an index of all the .MSG files to be sent.
 Av> 
 Av> On a successful post session using Spoon the REPLIES should be deleted.
 Av> But much like the error with Soupgate importing messages the REPLIES file
 Av> remained undeleted.

Well, a thing to try is to build it with one of the memory
sanitizers turned on and see if you can find the location
of the first free and the second; simply nil'ing out the pointer
will likely move past _that_ problem, as free(NULL) is a no-op.
But a more general problem is that none of this stuff was written
to be memory safe; short of a substantial refactoring of the
code, I suspect things like this will keep cropping up.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.