Subj : Re: Compiling from source
To   : Oli
From : Avon
Date : Sat Jan 30 2021 10:05:28

On 29 Jan 2021 at 08:43p, Oli pondered and said...
 
 Ol>  A> Came across a tool called Clang that has a -fsanitize=address option
 Ol> 
 Ol> That's a C compiler.

Oh OK, yeah I was trying to find a tool to follow up on Tensers suggestion of
looking for the double free memory issue.

I can understand how it can be a pain to try and track down as (if I
understand this right) we're essentially looking for locations across the
code where a variable is being called again but has already been
closed/nulled? It seems like there are tools about that can check the code on
compile and alert to hints as to where/what may be going on?

 Ol>  A> 2 warnings generated.
 Ol> 
 Ol> Compile time warnings. Easy to fix, but will not help with the NNTP bug.
 Ol> pop.cpp is for POP3 mail fetch.

Yep that's how I interpreted it also... interesting to see the issues in the
pop code, not that I use it... I've been trying to understand the nntp code
and the area around when a post is made and then the error occurs.

I'm a 2 year old trying to read a scientific novel :)

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

.