DNS utilities core dump in -current ?

[vom513 <vom513%gmail.com@localhost>]

I tried this in a -current from mid June as well as one from today.  Anything using the resolver library seems fine (ping/ssh/ftp).  But the DNS utilities (which my understanding is that they operate in a more “raw/direct” fashion bypassing the resolver lib) all fail.

Specifically I tried dig, delv, and nslookup:

c3700$ uname -a
NetBSD c3700.retronet.burn.net 11.99.1 NetBSD 11.99.1 (GENERIC) #0: Sun Aug  3 08:22:49 UTC 2025  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/hppa/compile/GENERIC hppa

c3700$ dig burn.net
assertion "!(urcu_memb_reader).registered" failed: file "/usr/src/external/lgpl2/userspace-rcu/lib/liburcu-memb/../../dist/src/urcu.c", line 486, function "urcu_memb_register_thread"
[1]   Abort trap (core dumped) dig burn.net

c3700$ delv burn.net
assertion "!(urcu_memb_reader).registered" failed: file "/usr/src/external/lgpl2/userspace-rcu/lib/liburcu-memb/../../dist/src/urcu.c", line 486, function "urcu_memb_register_thread"
[1]   Abort trap (core dumped) delv burn.net

c3700$ nslookup burn.net
assertion "!(urcu_memb_reader).registered" failed: file "/usr/src/external/lgpl2/userspace-rcu/lib/liburcu-memb/../../dist/src/urcu.c", line 486, function "urcu_memb_register_thread"
[1]   Abort trap (core dumped) nslookup burn.net

Obviously -current isn’t supposed to be completely stable - I’m just more curious as to what this is ?  Is there something in-progress changing that is causing this ?  It all looks to be something with liburcu ?

Thanks.