Re: signal SIGSEGV, Segmentation fault

[Richard Frith-Macdonald]

> On 22 May 2018, at 13:09, Andreas Höschler <ahoesch@smartsoft.de> wrote:
> 
> Hi Wolfgang,
> 
>> From the self pointer in the call frame:
>>  self=0xb7ca746e <-[NSView displayRectIgnoringOpacity:inContext:]+318>
>> gdb resolves this address to an address in the code of the 
>> displayRectIgnoringOpacity:inContext: method from the NSView class. :-)
> 
> Aha, interesting. But this still rings no bell (no idea how this could be).

Well, anything that overwrite the memory location in which 'self' is stored 
could cause this.
The most common thing (as suggested by Wolfgang) would be if the object was 
deallocated and the memory re-used (a retain/release error), but buffer 
overruns could also corrupt the memory.
Fred's suggestion of running under valgrind should help find the problem in 
either case.