[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gui apps segfault on Linux/x86/clang/libobjc2

From: Fred Kiefer
Subject: Re: gui apps segfault on Linux/x86/clang/libobjc2
Date: Wed, 5 Dec 2018 09:17:09 +0100

> Am 05.12.2018 um 08:50 schrieb Riccardo Mottola <address@hidden>:
> Fred Kiefer wrote:
>> The only thing that could go wrong from out side in this X call are the 
>> parameters that we provide. What you could try to do is to log the X display 
>> variable „dpy“ right before this call. I do not see how this could happen 
>> but maybe this is still not initialised with a sensible value.
> as what could I print out display? I tried as unsigned integer, in 
> [XGServerWindow iconSize]:
> 2018-12-05 08:36:00.264 Ink[8694:8694] styleoffsets ... guessing offsets
> 2018-12-05 08:36:00.273 Ink[8694:8694] styleoffsets ... guessing offsets
> 2018-12-05 08:36:00.470 Ink[8694:8694] iconsize - dpy 138629760
> 2018-12-05 08:36:00.471 Ink[8694:8694] iconsize - dpy 138629760
> Program received signal SIGSEGV, Segmentation fault.
> 0xb3ead101 in xcb_writev () from /usr/lib/libxcb.so.1
> is that where you would check? The stacktrace is corrupt and I can't get the 
> exact place of the call.

Yes, this is what I meant. Now you could compare this number to the display 
allocated for us in libs-back/Source/x11/XGServer.m at about line 422. Just 
print that out with a similar statement and the two numbers should match.
What is quite strange in your output is that this is reported twice. This looks 
like the icon size method gets called two times. This would mean that the first 
time this is handle correctly but fails the second time. could it be that these 
two calls happen at the same time? Could you also please print out the thread 
that is making these calls?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]