> On Aug 2, 2018, at 12:33 PM, ASV <[email protected]> wrote:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00001db26a5615d6 in change () from
> /usr/local/heimdal/lib/libkadm5srv.so.3.0
> Current language: auto; currently minimal
> (gdb) The program is running. Exit anyway? (y or n) n
> Not confirmed.
> (gdb) backtrace
> #0 0x00001db26a5615d6 in change () from
> /usr/local/heimdal/lib/libkadm5srv.so.3.0
> #1 0x00001db26a56155f in kadm5_s_chpass_principal_cond () from
> /usr/local/heimdal/lib/libkadm5srv.so.3.0
> #2 0x00001dafc3001b90 in ?? () from
> /usr/local/heimdal/libexec/kpasswdd
> #3 0x00001dafc3000996 in ?? () from
> /usr/local/heimdal/libexec/kpasswdd
> #4 0x0000000000000000 in ?? ()
>
> Any help would be highly appreciated.
> Thanks in advance.
1. Please rebuild heimdal with debugging symbols:
CFLAGS="-g -ggdb3 -O0"
that should make possible a stack trace with line numbers, ...
2. What happens when you try to change the password as root via
"kadmin -l cpw ..."? Does that work?
3. It might be helpful to know what HDB backend you're using.
4. Even without symbols you can ask GDB for the faulting instruction:
x/i $pc
and print the register values:
i reg
This may help to understand whether this a NULL pointer dereference,
or something else.
--
Viktor.
