Tim, Have you had time to look at this?
Josh Konkol, CNE MCSE Senior Network Analyst GuideOne Insurance Mail Stop AB-1 515-267-2427 [EMAIL PROTECTED] .~. /V\ /( )\ ^^-^^ -----Original Message----- From: Konkol, Josh [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 14, 2002 6:59 AM To: 'Tim Potter' Cc: Samba (E-mail) Subject: RE: [Samba] Samba 2.2.4 on s/390 OK, I think I got it right this time. print02p:/samba/var # ps -ae | grep winbind 26482 ? 00:00:00 winbindd print02p:/samba/var # gdb winbind 26482 This GDB was configured as "s390-suse-linux"...winbind: No such file or directory. /usr/local/samba/var/26482: No such file or directory. Attaching to Pid 26482 0x400f2e8a in ?? () (gdb) backtrace #0 0x400f2e8a in ?? () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x400ac8d6 in ?? () (gdb) backtrace #0 0x400ac8d6 in ?? () #1 0x4008d868 in ?? () (gdb) c Continuing. Program received signal SIGABRT, Aborted. 0x4006cd4e in ?? () (gdb) backtrace #0 0x4006cd4e in ?? () (gdb) c Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. Please let me know if you need anything else. Thanks sooo much for your help. Josh -----Original Message----- From: Tim Potter [mailto:[EMAIL PROTECTED]] Sent: Monday, May 13, 2002 6:07 PM To: Samba Subject: Re: [Samba] Samba 2.2.4 on s/390 On Mon, May 13, 2002 at 08:24:21AM -0500, Samba wrote: > Sorry for the multiple messages but I think I have got the back trace you > requested. I cleared the logs, restared the smb daemons, and ran gdb > winbindd <winbindprocid> . After the program started I hit 'c' to continue. > To cause the fault all I have to do is goto Start-Run and type \\print02p > (print02p is the instance name). At that point I started seeing output from > gdb. Below is the output. > > print02p:/samba # ps -ae | grep winbind > 24598 ? 00:00:00 winbindd > print02p:/samba # gdb winbind 24598 > GNU gdb 5.0 > <--snip licensing info--> > /usr/local/samba/24598: No such file or directory. > Attaching to Pid 24598 > 0x400f2e8a in ?? () > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x400ac8d6 in ?? () > (gdb) c > Continuing. > > Program received signal SIGABRT, Aborted. > 0x4006cd4e in ?? () > (gdb) c > Continuing. > > Program terminated with signal SIGABRT, Aborted. > The program no longer exists. Ah OK you're nearly there! Just type 'backtrace' into gdb and send me the output. This should contain the stack frames where winbindd crashed and is usually extremely helpful in tracking down these things. Tim. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
