I am fairly new to gdb. After I sleep it for 9000 or during that time, what should I collect? I did an smbstatus and saw the pid it reported for the connection and ran gdb smbd <pid#>. I stepped a bit through it and saw the stuff here (not sure if this is enough):
Program received signal SIGABRT, Aborted. 0xff19c724 in _libc_kill () from /usr/lib/libc.so.1 (gdb) n Single stepping until exit from function _libc_kill, which has no line number information. procfs: couldn't stop process 76253: wait returned -1 (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n procfs: fetch_registers, get_gregs line 3514, /proc/10717/lwp/1: No such file or directory. (gdb) n -----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
