Hi ! I'm currently testing gnustep in debian 10 (32 bit) with libobjc-2.0. I plan to try 64 bit version soon.
I've built ilt with clang-8 from
https://apt.llvm.org/ and with a script adapted from Patryck Laurent's ones (see attachment).
I've tested on real hardware and in a virtual machine and got the same errors.
Everything builds fine, base an gui pass test correctly and most apps run. But some tests fail in libobjc-2.0 :
19 - AssociatedObject_legacy (Child aborted)
20 - AssociatedObject_legacy_optimised (Child aborted)
Also, GWorkspace fails to load with the following error :
Unknown protocol versionAbort
I tried with debugapp and gdb and got the following backtrace :
bertrand@buster32:~/Bureau/GNUstep-build/libobjc2/build$ debugapp GWorkspace
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/GNUstep/Local/Applications/GWorkspace.app/GWorkspace...done.
(gdb) run
Starting program: /usr/GNUstep/Local/Applications/GWorkspace.app/GWorkspace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
Unknown protocol version
Program received signal SIGABRT, Aborted.
0xb7fd4d41 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7fd4d41 in __kernel_vsyscall ()
#1 0xb72ea382 in __libc_signal_restore_set (set=0xbfffde8c)
at ../sysdeps/unix/sysv/linux/internal-signals.h:84
#2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
#3 0xb72d42b6 in __GI_abort () at abort.c:79
#4 0xb75ce5b7 in init_protocols ()
from /usr/GNUstep/Local/Library/Libraries/libobjc.so.4.6
#5 0xb75cdc89 in objc_init_protocols ()
from /usr/GNUstep/Local/Library/Libraries/libobjc.so.4.6
#6 0xb75c987a in objc_load_class ()
from /usr/GNUstep/Local/Library/Libraries/libobjc.so.4.6
#7 0xb75cd55e in __objc_load ()
from /usr/GNUstep/Local/Library/Libraries/libobjc.so.4.6
#8 0xb76c275e in .objcv2_load_function ()
from /usr/GNUstep/Local/Library/Libraries/libgnustep-base.so.1.26
#9 0xb7fe6343 in call_init (l=<optimized out>, argc=argc@entry=1,
argv=argv@entry=0xbfffe264, env=0xbfffe26c) at dl-init.c:72
#10 0xb7fe6442 in call_init (env=0xbfffe26c, argv=0xbfffe264, argc=1,
l=<optimized out>) at dl-init.c:30
#11 _dl_init (main_map=<optimized out>, argc=1, argv=0xbfffe264,
env=0xbfffe26c) at dl-init.c:119
#12 0xb7fd70fa in _dl_start_user () from /lib/ld-linux.so.2
(gdb)
Last issue for now : rik.theme builds fine but doesn't display properly. I know rik uses objc_setAssociatedObject and objc_getAssociatedObject in its Rik+Button.m file.
Does anyone encounter these kind of issues