Re: pkg/59858: audio/pavucontrol broken

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

From: Ramiro Aceves <[email protected]>
To: [email protected], [email protected], [email protected],
 [email protected]
Cc: 
Subject: Re: pkg/59858: audio/pavucontrol broken
Date: Wed, 14 Jan 2026 22:03:23 +0100

 El 14/1/26 a las 18:55, Benny Siegert via gnats escribió:
 > The following reply was made to PR pkg/59858; it has been noted by GNATS.
 > 
 > From: Benny Siegert <[email protected]>
 > To: [email protected]
 > Cc: [email protected], [email protected], [email protected],
 >      [email protected], Taylor R Campbell <[email protected]>
 > Subject: Re: pkg/59858: audio/pavucontrol broken
 > Date: Wed, 14 Jan 2026 17:51:27 +0000 (UTC)
 > 
 >   On Wed, 14 Jan 2026, Ramiro Aceves via gnats wrote:
 >   
 >   > Thread 1 "" received signal SIGILL, Illegal instruction.
 >   > 0x0000f3cb73498e28 in ?? ()
 >   > (gdb)
 >   > (gdb) bt
 >   > #0  0x0000f3cb73498e28 in ?? ()
 >   > #1  0x0000ffffece41070 in _ctype_ () from /usr/libexec/ld.elf_so
 >   > Backtrace stopped: previous frame identical to this frame (corrupt stack?)
 >   > (gdb)
 >   
 >   Is this on -11 or current? If so, pavucontrol may be using the ctype API
 >   wrong, which can now trigger a crash. There is an environment variable
 >   that you can set to disable this, but I don't remember its name. Try
 >   searching the email archives.
 >   
 >   --
 >   Benny
 >   
 
 Hi Benny, thanks for answering
 
 It is on 10.1. I have read this on the archives:
 
 netbsd-nuc$ LIBC_ALLOWCTYPEABUSE="TRUE" pavucontrol
 
 But no luck, it seems to be only for NetBSD-11, not for NetBSD-10.1
 
 
 ENVIRONMENT
 
       In NetBSD 11, the ctype functions will always crash with a signal 
 on cer-tain invalid inputs as a diagnostic aid for applications; see 
 CAVEATS.
       Setting the environment variable LIBC_ALLOWCTYPEABUSE before 
 starting a program will restore the old behavior of returning nonsense 
 answers for these inputs, or sometimes but not always crashing, 
 depending on factors such as address space layout randomization.
 
 Regards.
 Ramiro.