Re: GWorkspace and new ABI

[Ivan Vučica]

Sorry for not responding, this was in spam.

Eyeballing for 2-3min, and nothing stands out. Correct libobjc.so.4.6 seems to be used.

1. Try using gdb to run GWorkspace (I'd guess gdb /usr/GNUstep/Applications/GWorkspace.app/GWorkspace should do the trick). Then when it inevitably calls abort(), you'll be dropped into gdb's CLI. Type 'bt' to get the backtrace which will tell you which library tried to access a bad protocol.

It still won't tell you which protocol is that, but it's a start.

2. If you haven't done things like that before and don't have time/will to try it now, and if you previously had GNUstep on the machine, I'd try to nuke /usr/GNUstep and possibly ~/GNUstep/Library/Libraries, then /etc/GNUstep.conf. Then reinstall from scratch. 

Not sure what else to look at, but there's more capable people on this mailing list than me, and you can always try to debug this further yourself :-)

pon, 7. lis 2019. u 14:54 Johannes Brakensiek <johannes@brakensiek.info> napisao je:

Hi Ivan,

thank you for your support. And yep, that line from protocl.c I found as
well...

So this is the output I get from strace:
https://gist.github.com/Letterus/01d913d85098c48d2183ed6de30abc40

Maybe you are able to detect anything unregular? For me it looks a
little bit weird that it's linked against libgcc, but other apps that
are as well, are working for me.

Johannes


Am 07.10.19 um 15:35 schrieb Ivan Vučica:
> (FWIW I'd guess it's
> this https://github.com/gnustep/libobjc2/blob/369c84d/protocol.c#L224 --
> even the newline missing matches -- which would indeed suggest an
> incompatible library being loaded. Perhaps something that shipped with
> gcc's objective-c support. I'd suggest stracing as above, or ldding.)
>
> On Mon, Oct 7, 2019 at 2:33 PM Ivan Vučica <ivan@vucica.net
> <mailto:ivan@vucica.net>> wrote:
>
>     I usually try to see what files are getting accessed using things
>     like:
>
>     strace GWorkspace 2>&1 | grep open
>
>     Usually because it's slightly more comprehensive than just seeing
>     what the executable is linked with using ldd.
>
>     On Sat, Oct 5, 2019 at 3:29 PM Johannes Brakensiek
>     <johannes@brakensiek.info <mailto:johannes@brakensiek.info>> wrote:
>
>         Hello everyone,
>
>         I've got some build problems again. ;-)
>
>         I managed to compile GNUstep on Debian Buster using the
>         current runtime
>         version from GitHub (new ABI). Most apps start and work fine.
>         But trying
>         to use GWorkspace I get this error:
>
>         $ GWorkspace
>         Unknown protocol versionAbgebrochen (which means: Cancelled)
>
>         Do you know if GWorkspace is doing anything different than
>         other apps?
>         Is this a linking problem (again)? I.e. is make trying to link
>         this one
>         against the wrong libraries? I do not know and also don't know
>         how to
>         debug this yet. :-)
>
>         Thanks and regards
>         Johannes
>
>         P.S.: This is the build script:
>         https://github.com/plaurent/gnustep-build/blob/master/debian-10-clang-8.0-runtime-2.0/GNUstep-buildon-debian10.sh
>
>
>
>         _______________________________________________
>         Discuss-gnustep mailing list
>         Discuss-gnustep@gnu.org <mailto:Discuss-gnustep@gnu.org>
>         https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
--
Johannes Brakensiek | Südseestr. 4 | 45357 Essen-Gerschede
Threema: P55HN6Z4
PGP-Schlüssel: <https://johannes.brakensiek.info/501AF234.asc>
PGP-Fingerabdruck: EFB4 319B F767 1655 2A62  F31B 74FD 2E7E 501A F234