Re: FYI: new X server in -current, among other X things

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

I wrote:
>
>>> [   378.033] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x44) [0x1467d46d5]
>>> [   378.033] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x79) [0x1467d0465]
>>> [   378.033] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0) [0x75b46379c930]
>>> [   378.034] (EE) 
>>> [   378.034] (EE) Segmentation fault at address 0x0
>>> 
>>> This happens with ctwm as part of the base installation, as well as with
>>> other pre-existing window managers and such from pkgsrc built against
>>> 9.99.97.
>>
>>can you configure X to generate a core dump or run it
>>under GDB and get the real stack trace?  i thought we'd
>>fixed this problem in libexecinfo, but it's still not
>>tracing through the SEGV above, so finding what is
>>crashing where is what we need next.
>
>FWIW, I get the same on my Pinebook with a lima kernel, this may not be
>i915 specific.
>
>Doing a full debug build now.

Building with MKDEBUG=yes stops it crashing, but it also stops glamor
from working.

I guess it is back to printf().