22 Jan
2015
22 Jan
'15
6:40 p.m.
On 22-Jan-2015 07:00, su_v wrote:
- Oddly, it seems that if the build has debug messages (to stdout) in
the source code related to retrieving the image resolution from file, the crash no longer happens.[2]
That is a classic symptom of a memory access violation - include a bit of extra code and bugs mysteriously disappear.
How to proceed?
I don't have a Mac so cannot help with this, but somebody needs to run that binary in gdb, trigger the crash, and then do a bt. It is usually evident from examining the code at the crash location where the memory access problem is. If valgrind works on OS X that would help too. (But I don't think it does.)
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech