Adrian, Thanks for the suggestions.
> Heap corruption is always mean to debug…
I agree.
I don't have proper debug tools to debug this. Hopefully clang will help.
I've never used clang so I'll read up and use it.
> It could be that your heap was already corrupted way
share the link here.
Heap corruption is always mean to debug…
It could be that your heap was already corrupted way earlier, but only the
“delete” notices that corruption which occurred for a totally independent
reason.
In general, I would recommend to enable address sanitizer in your compile
te: I simply construct the parser and delete it immediately - and get a
heap corruption error.Tracing thru the code, it looks like it is simply
establishing the stack (when creating the Parser).
Anyone have a similar issue? Any ideas are welcome.
I'll post anything anybody wants to look a
