> On Feb 8, 2018, at 12:43 AM, Eduardo <eduardo.mor...@mobelservices.com> wrote:
> Profiling shouldn't help, it isn't the rigth tool. Use Xcode analyzer or from
> command line scan-build and scan-view. If you can, use the last version of
> clang-analyzer.

The Clang address sanitizer would be the best tool for diagnosing memory 
corruption. It's a lifesaver.

In Xcode it's very easy to enable: go to the scheme editor, select Run (or 
Test) from the list on the left, click the Diagnostics tab, and click the 
"Address Sanitizer" checkbox. I also recommend checking "Detect use of stack 
after return" and "Malloc Scribble". Then press the Run (or Test) button. I 
tend to leave this on all the time while developing; it slows down the program, 
but not enough to get in the way.

It can also be used from the command-line, but I have no knowledge of how to do 
that. (I do know it requires recompiling with a special compiler flag, since it 
instruments the machine code.)

sqlite-users mailing list

Reply via email to