[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: signal SIGSEGV, Segmentation fault
From: |
Fred Kiefer |
Subject: |
Re: signal SIGSEGV, Segmentation fault |
Date: |
Wed, 30 May 2018 19:57:34 +0200 |
HI Andreas,
great that you could resolve your problem. I am still a bit confuse. Josh’s
mail was the first reply you did get for your problem report. Later you stated:
> 1) I have built GNustep on my own
> 2) I am using gcc and its runtime
In this scenario it wouldn’t be of any importance whether you use a current or
the old version of GNUstep make.
Now I really would like to understand what is going on here. Are you using
libobjc2 or the one from gcc? And if the former, which version?
Cheers,
Fred
> Am 30.05.2018 um 13:02 schrieb Andreas Höschler <ahoesch@smartsoft.de>:
>> On May 3, 2018, at 2:45 PM, Andreas Höschler wrote:
>>
>>> Segmentation fault
>>> ...
>>> while accessing one of its instance variables, actually in the
>>>
>>> NSLog(@"routeVisible: %d", _routeVisible);
>>>
>>> line. When I comment this line out I get the same error in the next line
>>> while accessing _routePath and so on. I am clueless how to fix this. The
>>> code works on MacOSX and also with on an ancient GNUstep/Debian/Kubuntu
>>> setup. Any idea what might cause this trouble on Ubuntu 16.04 with the
>>> latest GNUstep or how to further track this down?
>>
>>
>> Currently, libobjc2's non-fragile ABI can cause segfaults on Debian-based
>> distros (& perhaps other Linux distros) when directly accessing some class'
>> instance variables.
>>
>> There's a few workarounds for Ubuntu:
>>
>> * The Ubuntu install script on the wiki has a workaround (it checks out an
>> old version of GNUstep-make that builds using the fragile ABI):
>> http://wiki.gnustep.org/index.php/GNUstep_under_Ubuntu_Linux
>>
>> * If you need the non-fragile ABI, there's a script + objc2-patch attached
>> to this list message:
>> http://lists.gnu.org/archive/html/discuss-gnustep/2017-12/msg00129.html
>>
>> * David is working on a new ABI, and you can try his experimental builds:
>> http://lists.gnu.org/archive/html/gnustep-dev/2018-04/msg00051.html
>
> Thanks so much. That was the solution for my problem. The following lines
> extracted from your script got me a working GNUstep environment:
>
> apt-get install git-core
> git --version
> cd /usr/src/GNUstep
> git clone https://github.com/gnustep/tools-make.git
> cd tools-make
> git checkout `git rev-list -1 --first-parent --before=2017-04-06 master`
> ./configure --enable-debug-by-default --with-layout=gnustep
>
> . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh
>
> cd libs-base-master
> make distclean
> ./configure
> make
> make install
> cd ..
>
> cd libs-gui-master
> make distclean
> ./configure
> make
> make install
> cd ..
>
> cd libs-back-master
> make distclean
> ./configure
> make
> make install
> cd ..
>
> The standard installation without the make hack simply does not work at all
> on Ubuntu 16! :-(
>
> Thanks so much,
>
> Andreas
- signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/03
- Re: signal SIGSEGV, Segmentation fault, Josh Freeman, 2018/05/03
- 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, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Andreas Höschler, 2018/05/22
- Re: signal SIGSEGV, Segmentation fault, Wolfgang Lux, 2018/05/22