On 7 Jun 2019, at 18:27, Riccardo Mottola wrote:
>
> Hi,
>
>
> David Chisnall wrote:
>> It looks as if this protocol comes from NSDistributedNotificationCenter and
>> is created with an @protocol directive. With the gnustep-1.0 ABI, that is
>> attached to the
Hi,
David Chisnall wrote:
It looks as if this protocol comes from
NSDistributedNotificationCenter and is created with an @protocol
directive. With the gnustep-1.0 ABI, that is attached to the
__ObjC_Protocol_Holder_Ugly_Hack class and upgraded by the runtime.
It looks as if you've
On 05/06/2019 15:30, Riccardo Mottola wrote:
Hi David!
David Chisnall wrote:
Can you do a backtrace of where the crash is? What is the protocol
that it's inspecting while crashing?
of course... here it is:
Thanks.
Program received signal SIGABRT, Aborted.
0x0008028ca47a in
Hi David!
David Chisnall wrote:
Can you do a backtrace of where the crash is? What is the protocol
that it's inspecting while crashing?
of course... here it is:
Program received signal SIGABRT, Aborted.
0x0008028ca47a in thr_kill () from /lib/libc.so.7
(gdb) bt
#0 0x0008028ca47a
On 05/06/2019 05:30, Riccardo Mottola wrote:
Hi,
David Chisnall wrote:
On 04/06/2019 09:46, Riccardo Mottola wrote:
Hi David,
David Chisnall wrote:
Thanks for the report. Please can you file an issue on GitHub? This
is a quite surprising error - it implies that either clang has a bug
or
Hi,
David Chisnall wrote:
On 04/06/2019 09:46, Riccardo Mottola wrote:
Hi David,
David Chisnall wrote:
Thanks for the report. Please can you file an issue on GitHub?
This is a quite surprising error - it implies that either clang has
a bug or that something is trying to manually create
On 04/06/2019 09:46, Riccardo Mottola wrote:
Hi David,
David Chisnall wrote:
Thanks for the report. Please can you file an issue on GitHub? This
is a quite surprising error - it implies that either clang has a bug
or that something is trying to manually create or modify protocols
without
Hi David,
David Chisnall wrote:
Thanks for the report. Please can you file an issue on GitHub? This
is a quite surprising error - it implies that either clang has a bug
or that something is trying to manually create or modify protocols
without calling through the runtime. This might happen
On 04/06/2019 04:14, Riccardo Mottola wrote:
Hi,
I just upgraded all binary packages on FreeBSD using clang and packaged
libobjc2:
11.2-RELEASE-p10 FreeBSD 11.2-RELEASE-p10 #0: Mon May 13 21:20:50 UTC 2019
installed libobjc2 is:
libobjc2-2.0_1 Replacement Objective-C runtime
Hi,
I just upgraded all binary packages on FreeBSD using clang and packaged
libobjc2:
11.2-RELEASE-p10 FreeBSD 11.2-RELEASE-p10 #0: Mon May 13 21:20:50 UTC 2019
installed libobjc2 is:
libobjc2-2.0_1 Replacement Objective-C runtime
supporting modern Objective-C features
I
10 matches
Mail list logo
