[Samba] Samba 2.2.4 on s/390

Samba Samba at guidemail.com
Mon May 13 06:28:02 GMT 2002


Tim,

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.

Josh Konkol, CNE MCSE  
Senior Network Analyst
GuideOne Insurance
Mail Stop AB-1
515-267-2427
jkonkol at guidemail.com

 .~.
 /V\
/( )\
^^-^^



-----Original Message-----
From: Konkol, Josh 
Sent: Monday, May 13, 2002 7:58 AM
To: 'Tim Potter'
Subject: RE: [Samba] Samba 2.2.4 on s/390


Tim,

Thanks for the reply.

I have re-compiled Samba as you requested using:  ./configure.developer
--with-pam --with-winbind .  I then did make && make install.  I'm still
getting the error in log.winbindd.  

Excuse my newbieness but I don't know how to get a stack backtrace.  If you
give me instructions I will get it for you.

Thanks again,

Josh Konkol, CNE MCSE  
Senior Network Analyst
GuideOne Insurance
Mail Stop AB-1
515-267-2427
jkonkol at guidemail.com

 .~.
 /V\
/( )\
^^-^^



-----Original Message-----
From: Tim Potter [mailto:tpot at samba.org]
Sent: Sunday, May 12, 2002 7:29 PM
To: Konkol, Josh
Subject: Re: [Samba] Samba 2.2.4 on s/390


On Fri, May 10, 2002 at 08:19:09AM -0500, Konkol, Josh wrote:

> I have just compiled Samba 2.2.4 with the following configure.
> 
> ./configure --with-pam --with-winbind

> [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(38)
>   ===============================================================
> [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(39)
>   INTERNAL ERROR: Signal 11 in pid 26422 (2.2.4)
>   Please read the file BUGS.txt in the distribution
> [2002/05/10 08:04:35, 0] lib/fault.c:fault_report(41)
>   ===============================================================
> [2002/05/10 08:04:35, 0] lib/util.c:smb_panic(1092)
>   PANIC: internal error
> <End of File>

Hello.  Any chance of getting a stack backtrace from this?  If you
compile winbindd with -g also that would be good.  If you do a make
clean then ./configure.developer <other config args> it will build
winbindd and others with -g.


Tim.




More information about the samba mailing list