On 22 Sep 2015, at 5:44pm, Hugues Bruant <hugues at aerofs.com> wrote:
> Memory corruption seems unlikely: I would expect more errors to follow once > some piece of memory is corrupted. Valgrind is unfortunately not very > useful in this case as its OS X support is limited and it doesn't like JIT > very much. If a JVM is involved, you may not be using Xcode to write your program. But if you are using Xcode then it has memory-testing tools just as paranoid as valgrind built into it. Check out the 'Instruments' related to memory management. You may find this useful: <https://developer.apple.com/library/prerelease/mac/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/CommonMemoryProblems.html#//apple_ref/doc/uid/TP40004652-CH91-SW1> Simon.
