Subj : Compiling from source
To   : Avon
From : Oli
Date : Sat Jan 30 2021 08:53:21

Avon wrote (2021-01-30):

 A> On 29 Jan 2021 at 08:43p, Oli pondered and said...

 A>>> Came across a tool called Clang that has a -fsanitize=address
 A>>> option

 Ol>> That's a C compiler.

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

(of course Clang is also a C++ and Objective C compiler)

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

The compiler is the right tool for this. If I understand it correctly you would get the warnings / hints at runtime. Did you try to run the clang compiled spoon

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

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

I think it is in the socket.cpp code. There are a couple of deletes.

---
 * Origin: . (21:3/102)

.