11.0_BETA: glxinfo crashes with Segmentation fault

[Henryk Paluch <hpaluch%seznam.cz@localhost>]

Hello!

When I run just "glxinfo" on any machine (both virtual and bare metal) 
on 11.0_BETA - it appears to work but crashes on exit with Signal 11:

$ uname -a

NetBSD nbsd-sgate350.example.com 11.0_BETA NetBSD 11.0_BETA (GENERIC) 
#0: Sun Dec 14 14:19:17 UTC 2025  mkrepro@mkrepro.
NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64

$ glxinfo

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
(lot of output)
0x388 32 tc  0  32  0 r  y .   8  8  8  8 .  s  0 32  0  0  0  0  0  0 0 
None

[1]   Segmentation fault (core dumped) glxinfo

What is even more puzzling that I'm unable to get decent stack-trace 
(have installed all sets including debug).

$ gdb glxinfo glxinfo.core

Reading symbols from glxinfo...
Reading symbols from /usr/libdata/debug//usr/X11R7/bin/glxinfo.debug...
[New process 1979]
Core was generated by `glxinfo'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007b60f1d01eb3 in ?? ()
+bt
#0  0x00007b60f1d01eb3 in ?? ()
#1  0x00007b60f6b1795f in __cxa_finalize (dso=dso@entry=0x0) at 
/usr/src/lib/libc/stdlib/atexit.c:222
#2  0x00007b60f6b1753b in exit (status=0) at 
/usr/src/lib/libc/stdlib/exit.c:60
#3  0x0000000000b696d2 in ___start (cleanup=<optimized out>, 
ps_strings=0x7f7fff6dcfe0) at /usr/src/lib/csu/common/crt0-common.c:375
#4  0x00007f7ff77f08a8 in ?? () from /usr/libexec/ld.elf_so
#5  0x0000000000000001 in ?? ()
#6  0x00007f7fff6dc120 in ?? ()
#7  0x0000000000000000 in ?? ()
+q


Exactly using this NetBSD release: 
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-11/20251214141917Z/images/NetBSD-11.0_BETA-amd64-dvd.iso

My questions:

1. anybody else experiencing same crash on 11.0_BETA? (Just run 
"glxinfo" on your X11 session to test).
2. are there any hints how to get annotated stack trace from that crash?

Intuitively I suspect that this crash relates to Mesa libraries (because 
plain X11 commands work without problem), but I'm currently out of ideas 
how to find root cause.

Regards
  --Henryk Paluch