Subj : Re: Compiling from source
To   : tenser
From : Avon
Date : Wed Jan 27 2021 19:58:46

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

I confess I'm mostly stumbling around in the dark here hoping something will
work. My preference is to try to get the Linux code working if doable so as
to be able to keep using what (until now) has been a relatively straight
forward bit of software (for windows) and not have to figure out another more
bulky option I have yet to find.

I think the 32bit thing may have solved some of the issues... but problems
remain with both soupgate import and soup export/posting to NNTP. :(

 te>  Av> On a successful post session using Spoon the REPLIES should be delete
 te>  Av> But much like the error with Soupgate importing messages the REPLIES 
 te>  Av> remained undeleted.
 te> 
 te> Well, a thing to try is to build it with one of the memory
 te> sanitizers turned on and see if you can find the location
 te> of the first free and the second; simply nil'ing out the pointer
 te> will likely move past _that_ problem, as free(NULL) is a no-op.
 te> But a more general problem is that none of this stuff was written
 te> to be memory safe; short of a substantial refactoring of the
 te> code, I suspect things like this will keep cropping up.

Thank you for the guidance. I think Oli is perusing this and I'm trying to
get him some news / soup files to play with.

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

.