Re: apple m1 status update (20241122)

Hi,

On Fri, Nov 22, 2024 at 06:59:55AM +0900, Jun Ebihara wrote:
> X.Org X Server 1.21.1.7
> [    40.591] (EE) Backtrace:
> [    40.592] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x3c) [0x9761b8c]
> [    40.592] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x78) [0x975d4f8]
> [    40.592] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0)
> [0xf7d48807e1e8]
> [    40.592] (EE) 3: /usr/X11R7/bin/X (CreateColormap+0x418) [0x9644a68]
> [    40.592] (EE) 4: /usr/X11R7/bin/X (miCreateDefColormap+0x84) [0x96b7744]
> [    40.592] (EE) 5: /usr/X11R7/lib/modules/drivers/wsfb_drv.so
> (+0x147c) [0xf7d4874e322c]
> [    40.592] (EE) 6: /usr/X11R7/bin/X (AddScreen+0xac) [0x9639c6c]
> [    40.592] (EE) 7: /usr/X11R7/bin/X (InitOutput+0x26c) [0x967616c]
> [    40.592] (EE) 8: /usr/X11R7/bin/X (dix_main+0x1a0) [0x9608fd0]
> [    40.592] (EE)
> [    40.592] (EE) Segmentation fault at address 0xf7d487aa07f0
> [    40.592] (EE)
> Fatal server error:
> [    40.592] (EE) Caught signal 11 (Segmentation fault). Server aborting

This might well be an issue with libunwind.  I was debugging a very
similar backtrace at work (Linux and xvfb instead of NetBSD and X.Org,
but also aarch64) and it ended up being an issue in libunwind.
Updating to a more recent release of libunwind helped, but I can try
to track down the commit that fixed things, perhaps that's enough to
fix this for you too.


  Harold