Bug#512410: openssh-server: sshd segfaults (suppose libc or libpam-mount related)
"Livingston, John A" <email@example.com> writes:
> I couldn't (easily) convince sshd to create a core dump, so I just
> started it with gdb attached and then tried a password
> connect. Backtrace is below. Let me know if you want to me to dump out
> anything in particular from any of the frames.
> Program received signal SIGSEGV, Segmentation fault.
> _int_free (av=0x7ffff6653e60, p=0x55544952454d5845) at malloc.c:4892
> 4892 malloc.c: No such file or directory.
> (gdb) where
> #0 _int_free (av=0x7ffff6653e60, p=0x55544952454d5845) at malloc.c:4892
> #1 0x00007ffff634b87c in *__GI___libc_free (mem=<optimized out>)
> at malloc.c:3738
> #2 0x00007ffff68d182b in default_an_to_ln (
> context=context@entry=0x5555557fb040, aname=aname@entry=0x5555557fb650,
> lnsize=lnsize@entry=65, lname=lname@entry=0x7fffffffd760 "")
> at ../../../../src/lib/krb5/os/an_to_ln.c:632
Ugh. So it's segfaulting on a routine free(). That means memory
Can you try running sshd -d under valgrind and see if it can spot where
the memory corruption is happening?
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>