Re: signal SIGSEGV, Segmentation fault

2018-05-07 Thread Fred Kiefer
Am 07.05.2018 um 19:45 schrieb Andreas Höschler :
> 
>> before banging on the head, since your code is "ancient" could you try using 
>> gcc and its runtime if you are using clang+libobjc2.
>> 
>> This would mean however probably compiling all gnustep yourself.
> 
> 1) I have built GNustep on my own
> 2) I am using gcc and its runtime
> 
> !?? That's what presented me the app with the unexplainable segmentation 
> fault!?
> 
> Any idea?

Thank you for clarifying that you use gcc.

Could it be that self gets deallocated in the "bums" method call? The best way 
to find out about this would be to run the application with valgrind. Many 
mysterious problems became quite clear when looking at them through the 
valgrind toolset. If you require help with that, I could provide you with 
detailed instructions.
___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnustep


Re: signal SIGSEGV, Segmentation fault

2018-05-07 Thread Andreas Höschler
Hi Riccardo,

> before banging on the head, since your code is "ancient" could you try using 
> gcc and its runtime if you are using clang+libobjc2.
> 
> This would mean however probably compiling all gnustep yourself.

1) I have built GNustep on my own
2) I am using gcc and its runtime

!?? That's what presented me the app with the unexplainable segmentation fault!?

Any idea?

Thanks,

 Andreas

___
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnustep