[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: signal SIGSEGV, Segmentation fault
From: |
Wolfgang Lux |
Subject: |
Re: signal SIGSEGV, Segmentation fault |
Date: |
Tue, 22 May 2018 12:35:41 +0200 |
Am 22.05.2018 um 11:31 schrieb Andreas Höschler <ahoesch@smartsoft.de>:
> Any further ideas?
Looking back at your initial report, it has this telling line about the crash:
Thread 1 "TimberNav" received signal SIGSEGV, Segmentation fault.
-[MapView drawRect:] (self=0xb7ca746e <-[NSView
displayRectIgnoringOpacity:inContext:]+318>,
_cmd=0x8a704b8, rect=...) at MapView.m:168
168 NSLog(@"routeVisible: %d", _routeVisible);
(gdb)
The self parameter in the call is a pointer into the code area of the program.
So it looks like a serious memory management issue in your program where the
MapView object that you intended to call the drawRect: method on has been
released already and its memory been overwritten by some other code.
Perhaps adding NSZombieEnabled=YES to the environment before running your
program might already give you a clue.
Wolfgang
- Re: signal SIGSEGV, Segmentation fault, (continued)
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/04
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/07
- Re: signal SIGSEGV, Segmentation fault, Fred Kiefer, 2018/05/07
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/08
- Re: signal SIGSEGV, Segmentation fault, Fred Kiefer, 2018/05/08
- Re: signal SIGSEGV, Segmentation fault, Andreas Fink, 2018/05/09
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault,
Wolfgang Lux <=
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Wolfgang Lux, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Fred Kiefer, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Richard Frith-Macdonald, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Richard Frith-Macdonald, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/22