Re: kpasswdd dumps on OpenBSD6.3
Viktor Dukhovni <[email protected]> Sat, 4 Aug 2018 14:43:45 -0400
| Newsgroups | gmane.comp.encryption.kerberos.heimdal.general |
|---|---|
| Message-ID | <[email protected]> |
On Aug 4, 2018, at 2:05 PM, ASV <[email protected]> wrote: > On Fri, 2018-08-03 at 14:05 -0400, Viktor Dukhovni wrote: >>> On Aug 3, 2018, at 1:43 PM, ASV <[email protected]> wrote: >>> >>> No, no crashes using "kadmin -l". >> >> This shows that "kadmin" and the libkadm5srv.so library work fine. >> >> Which libraries is "kadmin" linked with (post ldd output)? > # ldd /usr/local/heimdal/bin/kadmin > /usr/local/heimdal/bin/kadmin: [ Thanks, same libraries for both ] > >> Which libraries is "kpasswdd" linked with (post ldd output) and make >> sure you're reporting the results for the right executable. > # ldd /usr/local/heimdal/libexec/kpasswdd > /usr/local/heimdal/libexec/kpasswdd: > Start End Type Open Ref GrpRef Name [ Ditto ] > And yes, these are the right executable called by the rc scripts. So change() in /usr/local/heimdal/lib/libkadm5srv.so.3.0 works when invoked via "kadmin -l cpw", but segfaults via "kpasswdd", with a likely NULL kadm5 handle. We can confirm the guess about the NULL handle by printing more of the machine instructions of change(). If the crash is still at change+102, please report the output of (first one confirms the 102 offset, adjust the next if different): x/i $pc x/40i $pc-102 This should indicate what happened in change() before the crash. But really, at this point symbols are needed, and we'd need to look up the call stack to see how the handle got to be NULL. > About this I do not know what to say, I've seen the CFLAGS in the > compiling output lines and I even posted in the email. > I will try again as soon as I can. That seems to be the main path forward. -- Viktor.