[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: signal SIGSEGV, Segmentation fault
From: |
Riccardo Mottola |
Subject: |
Re: signal SIGSEGV, Segmentation fault |
Date: |
Tue, 22 May 2018 15:18:56 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 |
Hi,
Andreas Höschler wrote:
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!?
where does bums come from?
It looks really strange that self is null.
I would look up the alloc/init chain to check if somewhere an init
return nil for some error.
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. :-(
GCC/Linux works fine, I test it in a lot of places.
Specifically, Ubuntu LTS/GCC/Linux work fine for me on x86 on every
application I tried on. I am away for work for a week, on my retour I
can give you exact configuration details.
To me it really smells that your custom app has some kind of issue I
can't spot or triggers a strange GNUstep behaviour.
Did you try running other application and "stress" your environment a
bit? Try from simple Ink to using Terminal and GWorkspace. Those will
stress a little bit.
GCC works well for me on most platforms I used, except currently on
FreeBSD where I have strange issues (surely most work is tone there with
clang and libobjc2).
You might want to set up a VM with NetBSD and essential GNUstep
environment to test it, just as a comparison. However, I my "guts" tell
me that it must work just as fine on Ubuntu.
Riccardo
NetBSD and OpenBSD are very reliable for me with GCC.
- Re: signal SIGSEGV, Segmentation fault, (continued)
- 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, 2018/05/22
- 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 <=
- 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
- Re: signal SIGSEGV, Segmentation fault, Yavor Doganov, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Riccardo Mottola, 2018/05/22