Re: signal SIGSEGV, Segmentation fault

[Fred Kiefer]

That looks interesting. Could you please add a view more outputs of self before 
this line. EG, at the start of the method, after the super call and after the 
[self image] call. I suspect one of these will corrupt self.

Fred

> Am 22.05.2018 um 14:38 schrieb Andreas Höschler <ahoesch@smartsoft.de>:
> 
> Hi all,
> 
> I just added
> 
> - (void)drawRect:(NSRect)rect
> {
>    NSLog(@"MapView drawRect %@ ... _osmDrawing %d", NSStringFromRect(rect), 
> _osmDrawing);
>    [super drawRect:rect];
>    NSLog(@"After super drawRect:rect");
> 
>       NSImage *image = [self image];
>       NSSize imageSize = [image size];
>       
>       NSLog(@"asasa %@", self);  // <--- this line
> 
>       NSLog(@"routeVisible: %d", _routeVisible);
>       NSLog(@"routePath: %@", _routePath);
> 
> }
> 
> and get
> 
> 2018-05-22 14:32:37.291 TimberNav[10763:10763] MapView drawRect {x = 0; y = 
> 0; width = 817; height = 334} ... _osmDrawing 0
> 2018-05-22 14:32:37.291 TimberNav[10763:10763] After super drawRect:rect
> 2018-05-22 14:32:37.291 TimberNav[10763:10763] bums
> 2018-05-22 14:32:37.291 TimberNav[10763:10763] asasa (null)
> 
> before the app crshes while accessing the ivar _routeVisible. So what does 
> that mean? This looks like a very serious issue with the OS, gcc, objc to 
> me!? 
> 
> This brings me back to the question of a reliably working Linux, GNUstep 
> combo? If I could I would revert back to my ancient GNUstep tree (that worked 
> at least) but the ancient GNUwtep sources do no longer build on Ubuntu which 
> leaves me in a void. :-(
> 
> Best wishes,
> 
>  Andreas
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep