On 2024-03-05 1:13 am, matthew green wrote:
ah. the problem is that struct isc_nmhandle grew a pointer member,
adding 4 bytes to the struct size, and it uses C99 [] variable array
for the final member, which is later assigned to other pointers, and
this memory was now only 4-byte aligned. this
On 2024-03-05 1:13 am, matthew green wrote:
ah. the problem is that struct isc_nmhandle grew a pointer member,
adding 4 bytes to the struct size, and it uses C99 [] variable array
for the final member, which is later assigned to other pointers, and
this memory was now only 4-byte aligned. this
On Tue, 5 Mar 2024, John D. Baker wrote:
> Thanks for the rapid analysis and workaround. I've applied it to my
> netbsd-10 tree, rebuilt sparc and am updating now.
It seems to be working now. Thanks again.
--
|/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X
|\ /
On Tue, 5 Mar 2024, matthew green wrote:
> ah. the problem is that struct isc_nmhandle grew a pointer member,
> adding 4 bytes to the struct size, and it uses C99 [] variable array
> for the final member, which is later assigned to other pointers, and
> this memory was now only 4-byte aligned.
ah. the problem is that struct isc_nmhandle grew a pointer member,
adding 4 bytes to the struct size, and it uses C99 [] variable array
for the final member, which is later assigned to other pointers, and
this memory was now only 4-byte aligned. this hack patch works to
stop named crashing for
this appears to be a badly aligned structure issue. i can reproduce
it by doing "anita interact" with any recent sparc .iso, editing the
named.conf to start, starting named, and doing 'dig ns netbsd.org'
would trigger the crash.
the stack trace is:
(gdb) bt
#0 ns__client_request
actually, i found a core file in /var/chroot/named/etc/namedb/named.core.
my build is missing debug info so i don't have a good idea what.
.mrg.
> Unfortunately there was no core dump.
this is almost certainly because /var/chroot/named is not writeable
by user named, which is on purpose.
you can set the corefile path for this process after it starts using
sysctl proc.$pid.corename. i think setting to "/var/tmp/%n.core"
should allow it
John D. Baker wrote:
> Sure enough, 'named' wasn't running. Checking the logs found
> that some options in "named.conf" were no-longer available.
>[...]
> Has anyone else seen anything similar with the new BIND in -current
> and since pulled up to 10.0_RC5?
I noticed the same, both for RC5
