Re: libobj2 changes

[Andreas Fink]

Yes I recompiled everything from scratch on a new empty VM.
I don't think its a bug in libobjc2 but more a changed behaviour which
has a side effect in my application.

I have been through the hell of incorrectly compiled libraries a couple
of times before (not compiling with right clang or gold linker etc) and
I know these pitfalls.
The make check's however all succeed (except the ones which always fail
in some date formatting area which are really edge cases which are not
really relevant).  So I doubt its a compilation issue. And in this case
its the same compiler I use all the time and the same operating system
version (Debian 10).

I don't get any crashes. Everything looks good from the outside. Just my
application (which does a lot of network communications via SCTP
sockets) starts to fail  by loosing communication links. And this stuff
is nothing really special. Its heavily multithreaded (with the matching
locks etc) and throws exception when it tries to send data and the
socket returns an error (link down, buffer full etc etc) which then are
catched further up. If a new kind of exception is thrown in such a case,
it could terminate the thread. Thats why I'm on the lookout for what has
changed exactly which could result in such a scenario. I'm pretty sure
it's super easy to fix but currently hard to find. Thats why I'm looking
for clues & hints on where to look more closely.


David Wetzel wrote on 31.05.21 17:04:
> Hi Andreas,
>
> Did you recompile everything? Are your binaries using the correct libraries?
>
> Dave
>
> Von meinem iPhone gesendet
>
>> Am 2021-05-31 um 10:56 schrieb Andreas Fink <afink@list.fink.org>:
>>
>> Hello all,
>>
>> I upgraded my gnustep and libobjc libraries to the latest version and I
>> suddenly get strange effects in my app that internal communication is
>> lost and reestablished all the time. I suspect some new exceptions being
>> thrown I don't catch properly and thus threads are ending or the like.
>> The release notes to libobjc2  hint some changes in this area.
>>
>> I wonder what the easiest way would be to debug such an issue. I often
>> trow NSException in my communication processing code (if packets are
>> wrong, can not be decoded, sockets are closed and the like) and catch it
>> further up. But there must be some new exceptions out there which are
>> thrown which wherent before which I don't catch correctly and I wonder
>> what I could have missed.
>>
>> Note: the application is not crashing or quitting...
>>
>> If you have any good idea on how to diagnose such a problem, let me know.
>>
>> My working release of libobjc2 is 1.9
>> The new one is from the repo (2.1 currently)
>>
>>
>>
>>