On Tue, Jan 07, 2014 at 05:48:16PM -0500, Pat Suwalski wrote: > It is surprisingly difficult to get a stack trace, even with > samba-dbg and heimdal-dbg installed:
> #0 0x0000000000000000 in ?? () > #1 0x00007f58b4821ff5 in ?? () > #2 0x00007fff2c599618 in ?? () > #3 0x00007f58ba31f260 in ?? () > #4 0x00007f58ba8e57e0 in ?? () > #5 0x00007f58ba2c6280 in ?? () > #6 0x00007f58ac129a29 in ?? () from /usr/lib/x86_64-linux-gnu/libhdb.so.9 > #7 0x0000000000000008 in ?? () > #8 0x00007f58bb7ef320 in ?? () > #9 0x00007f58ac117f40 in ?? () from /usr/lib/x86_64-linux-gnu/libhdb.so.9 > #10 0x00007fff2c599690 in ?? () > #11 0x0000000096c73af9 in ?? () > #12 0x00000000bff03a27 in ?? () > #13 0x0000000000000000 in ?? () > Perhaps I am missing something obvious to get more output? gdb does > mention they are loaded: > Reading symbols from /usr/lib/x86_64-linux-gnu/libhdb.so.9...Reading > symbols from > /usr/lib/debug/usr/lib/x86_64-linux-gnu/libhdb.so.9.2.0...done. > done. > Loaded symbols for /usr/lib/x86_64-linux-gnu/libhdb.so.9 > That happened with the samba server in PDC mode, running "passwd" > via sssd or changing the password via Windows 8. I'm sorry to say that this stack trace shows signs of stack corruption. "0x0000000000000000" and "0x0000000000000008" are not valid addresses to appear in a backtrace. You may have better luck debugging by running under valgrind, which can often detect stack corruption errors at runtime /before/ they clobber the stack. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
