On 4/09/23 22:30, Taylor R Campbell wrote:
Can you share `ldd /usr/libexec/kadmind' on the machine where it's
crashing? Wondering whether it's mixing shlib versions in one address
space, like https://gnats.netbsd.org/57603 (though that's not the same
issue because you're only using things in base).
/usr/libexec/kadmind:
-lgssapi.11 => /usr/lib/libgssapi.so.11
-lkrb5.27 => /usr/lib/libkrb5.so.27
-lhx509.6 => /usr/lib/libhx509.so.6
-lasn1.10 => /usr/lib/libasn1.so.10
-lcom_err.8 => /usr/lib/libcom_err.so.8
-lc.12 => /usr/lib/libc.so.12
-lroken.20 => /usr/lib/libroken.so.20
-lutil.7 => /usr/lib/libutil.so.7
-lcrypt.1 => /usr/lib/libcrypt.so.1
-lcrypto.15 => /usr/lib/libcrypto.so.15
-lwind.1 => /usr/lib/libwind.so.1
-lheimbase.2 => /usr/lib/libheimbase.so.2
-lsqlite3.1 => /usr/lib/libsqlite3.so.1
-lm.0 => /usr/lib/libm.so.0
-lheimntlm.5 => /usr/lib/libheimntlm.so.5
-lkadm5srv.15 => /usr/lib/libkadm5srv.so.15
-lhdb.15 => /usr/lib/libhdb.so.15
Can you install the debug set on one of the affected systems where you
can reproduce a problem to get more information out of the stack
traces?
I'll rebuild a tree with MKDEBUG and MKDEBUGLIB set now, and see what I see.
cheers
mark
