Re: libobjc2-clang

[Riccardo Mottola]

Hi David, hi Wolfgang,


David Chisnall wrote:
> Wow, I ignored email for a week and there are 50 unread emails in my GNUstep 
> folder!  Great to see some renewed interest and activity in the project!

well, perhaps one of the effect of virus lockdown was to have more time 
to hack again! At least for me it is the case... update a lot systems 
that I did not have time for... wrote code and discovered new pitfalls.
I hope you all are fine.

> > how can I print out this?
> > (gdb) p protocols
> > $4 = (struct objc_protocol_list *) 0x753c816c91b0 <objc_protocol_list>
> >
> > just to know which "list" and what should be loaded, I suppose there is an 
> > error here.
> This is the protocol list that is currently being initialised.  It would be 
> interesting to see what `i` is (I guess 0), because they tells us if we’re failing on 
> the first protocol in a class or a subsequent one.  Then look at `version`, which 
> should be a protocol version number.  If it isn’t a small value (<16), look at 
> `aProto->isa`.

you guessed correctly and the protocol is also a very common one, NSCopying

(gdb) p *protocols
$4 = {next = 0x0, count = 2, list = 0x7b8aa32ea1c0 <objc_protocol_list+16>}

(gdb) p i
$1 = 0
(gdb) p aProto
$2 = (struct objc_protocol *) 0x7b8aa39138b8 <._OBJC_PROTOCOL_NSCopying>


version is small:
(gdb) p version
$3 = 0



> Can you also confirm whether you’ve built with OLDABI_COMPAT enabled?  If you 
> didn’t, then you’ll see this message if you try to load any code that isn’t 
> compiled with the v2 ABI.

I confirm OLDABI_COMPAT is on. I did not touch it. LEGACY_COMPAT is off.

I only changed the linker option and then the build type.

Further question: this is a from-scratch install, all compiled with the 
same version of clang, can I assume that all libraryes have the same ABI 
or not? maybe there is a makefile issue somewhere?

Thanks,

Riccardo