Re: bin/59035: new named(8) crashes at startup on evbarmv5

["Tobias Nygren via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR bin/59035; it has been noted by GNATS.

From: Tobias Nygren <tnn%NetBSD.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: Martin Husemann <martin%NetBSD.org@localhost>
Subject: Re: bin/59035: new named(8) crashes at startup on evbarmv5
Date: Sun, 16 Feb 2025 00:42:31 +0100

 Something might be going awry with liburcu's ELF constructors
 when it is linked into named as a static library. The
 thread_call_rcu_data pointer which is supposed to be inited by the
 constructor contains apparent garbage at startup.
 
 The easiest workaround seems to be to remove the constructor.
 I think this is safe because rcu_register_thread calls rcu_init
 regardless ...
 
 Martin, does this help on earmv5?
 (May be need to clean obj/external/{lgpl2,mpl} manually)
 
 --- external/lgpl2/userspace-rcu/dist/src/urcu.c	17 Jan 2025 16:00:50 -0000	1.1.1.1
 +++ external/lgpl2/userspace-rcu/dist/src/urcu.c	15 Feb 2025 23:38:07 -0000
 @@ -83,7 +83,7 @@ static int urcu_memb_has_sys_membarrier_
  int urcu_memb_has_sys_membarrier = 0;
  #endif
 
 -void __attribute__((constructor)) rcu_init(void);
 +void rcu_init(void);
  #endif
 
  #if defined(RCU_MB)