Don't step at that point. The process has already run the CPU into the wrong segment, or accessed memory using a bad pointer. Stepping will only destroy information.
Do a 'bt' instead. That will dump the call stack, and show what path the code ran to get to this point. What I expect to see is somewhere above the strcmp routine, a Samba routine will call strcmp with a bad pointer, or a non-terminated string buffer. We need to know which routine did that.
-----Original Message-----
From: David Shapiro [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 9:17 AM
To: 'Andrew Bartlett'; David Shapiro
Cc: 'Richard Sharpe'; '[EMAIL PROTECTED]'
Subject: RE: sessionid.tdb missing after build and client read failutre
Trying to get better at this gdb here. I see a segmentation fault:
which has no line number information.
Program received signal SIGSEGV, Segmentation fault.
0xff132e84 in strcmp () from /usr/lib/libc.so.1
(gdb) step
Single stepping until exit from function strcmp,
which has no line number information.
0xff1544ec in _tzload () from /usr/lib/libc.so.1
(gdb) step
Single stepping until exit from function _tzload,
which has no line number information.
0xff152df8 in _ltzset_u () from /usr/lib/libc.so.1
(gdb) step
Single stepping until exit from function _ltzset_u,
which has no line number information.
0xff152994 in mktime () from /usr/lib/libc.so.1
(gdb) step
Single stepping until exit from function mktime,
which has no line number information.
0xff1736dc in strftime () from /usr/lib/libc.so.1
(gdb) step
Single stepping until exit from function strftime,
which has no line number information.
0x136db0 in timestring ()
(gdb) step
Single stepping until exit from function timestring,
-----Original Message-----
From: Andrew Bartlett [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 9:01 AM
To: David Shapiro
Cc: 'Andrew Bartlett'; 'Richard Sharpe';
'[EMAIL PROTECTED]'
Subject: Re: sessionid.tdb missing after build and client read failutre
David Shapiro wrote:
>
> Thank you Andrew. I was looking at joining because it was mentioned that
to
> get sessionid.tdb, you needed to join domain. I looked ing smbd.log and
saw
> a connection from davidsha, and then in my workstation log and saw at the
> bottom:
>
> ===============================================================
> [2002/07/02 08:40:53, 0] lib/fault.c:fault_report(37)
> INTERNAL ERROR: Signal 11 in pid 8127 (3.0-alpha17)
> Please read the file BUGS.txt in the distribution
> [2002/07/02 08:40:53, 0] lib/fault.c:fault_report(39)
> ===============================================================
>
> I also keep getting an xterm session pop up that says:
>
> xterm: Can't execvp /usr/local/bin/gdb
>
> I think this comes from the line in smb.conf:
>
> panic action = /usr/openwin/bin/xterm -display $DISPLAY -e
> /usr/local/bin/gbd -p %d
>
> gdb is in /usr/local/bin. What does it mean it can't execvp it?
I dunno - but just make it a simple 'panic action = /bin/sleep 9000' and
attach manually. Then lets look at it from there.
Andrew Bartlett
--
Andrew Bartlett [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED]
Student Network Administrator, Hawker College [EMAIL PROTECTED]
http://samba.org http://build.samba.org http://hawkerc.net
