Mailing List Archive

miata and samba3
Hello,

I am new to this list, luckily not new to Linux and Gentoo (I386) a bit
newer to Alpha.

I am and was able to get a PWS 500au (miata) booting and running (saw
some problems in the archive about booting maybe I have some answers if
still needed).

The problem I run into is with Samba (3.0.9-r1 as well 3.0.10) it
compiles well (fails on smbtorture, but ok) runs fine and seems oke but
when trying to place a file on the fileshare ,for a windows client, it
fails warning about the network name no longer available, still creates
an empty file, when looking in the log file it states a INTERNAL ERROR
Signal 11 and stating it should be submitted as a bug, but with the same
system running on a dual-xeon no problem.

are there any alpha + samba users and which config (versions) do you
run? any hints to a solution?

for reference:
PWS 500au (PWS 433a up next) from stage1
kernel 2.4.21-alpha-r9
samba 3.0.9-r1 / 3.0.10
make.conf:
CFLAGS="-mcpu=ev56 -O3 -pipe" and tried "-mcpu=ev4 -pipe" for samba
MAKEOPTS="-j2"
USE="-X alsa cdr ethereal mysql oss ldap"

With regards,

Edwin Barendse


--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
Hello Edwin,

>The problem I run into is with Samba (3.0.9-r1 as well 3.0.10) it
>compiles well (fails on smbtorture, but ok) runs fine and seems oke but
>when trying to place a file on the fileshare ,for a windows client, it
>fails warning about the network name no longer available, still creates
>an empty file, when looking in the log file it states a INTERNAL ERROR
>Signal 11 and stating it should be submitted as a bug, but with the same
>system running on a dual-xeon no problem.
>
>

I'm having _exactly_ the same problem on my Alpha XL 366. I originally
was running Samba 3.0.9-r1, which had the problem, and yesterday I
upgraded to 3.0.11 to see if that would help, but it didn't. The problem
still exists.

FYI, I have searched Google, and found no specific info on Samba and
Signal 11, but what I did find was that Signal 11 (segfault) often
happened when you have bad RAM. The thing is, only Samba ever exhibits
that problem, so I don't think I have bad RAM or it would happen more
randomly than that.

Perhaps someone more versed in Samba could help us. In particular, I
know that when I installed Samba, I used the same config file I used on
another install (another version of Samba, which was running on
Debian-Alpha at the time). The config file seems to work fine (Samba
doesn't complain, even when I do 'testparm') but I don't know if that
could be a source of the problem. I am including my smb.conf just to see
if someone could spot something that might cause this problem...

Anyways, if you ever find something, please let me know. I'll do
likewise. And if anyone on the list has ever had this problem or can
otherwise help us, we'd like to hear from you!

Thanks in advance,

J-S

--
___________________________________________
Jean-Sébastien Guay jean_seb@videotron.ca
http://whitestar02.webhop.org/
Re: miata and samba3 [ In reply to ]
Signal 11, Segmentation Faults are usually either
1) Program bugs
2) Bugs introduced by compiler optimizers

One of the previous messages in this thread showed
someone using -O3 in their CFLAGS. You could try
bumping the optimization level down to -O2 and see if
that fixes anything. Short of that, the only way to
figure it out for sure is to do some debugging of
Samba with gdb. Getting a core file would be a start.

Jeff D




__________________________________
Do you Yahoo!?
Take Yahoo! Mail with you! Get it on your mobile phone.
http://mobile.yahoo.com/maildemo

--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
Hi Jeff,

>Signal 11, Segmentation Faults are usually either
>1) Program bugs
>2) Bugs introduced by compiler optimizers
>
>One of the previous messages in this thread showed
>someone using -O3 in their CFLAGS. You could try
>bumping the optimization level down to -O2 and see if
>that fixes anything. Short of that, the only way to
>figure it out for sure is to do some debugging of
>Samba with gdb. Getting a core file would be a start.
>
>

In my case, here's the relevant part of my make.conf :

CFLAGS="-mieee -O2 -mcpu=ev56 -pipe"
CHOST="alphaev56-unknown-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"

I think that's relatively conservative.

Other than that, how do I get a core file? I assume there's something I
need to enable so that programs will dump core when a segfault occurs,
but I don't know what. But other than providing a core file and
answering questions about my config, there isn't much I can do to zero
in on the problem since I don't know how to use gdb (to get anything
meaningful, in any case...)

Thanks for your help,

J-S

--
___________________________________________
Jean-Sébastien Guay jean_seb@videotron.ca
http://whitestar02.webhop.org/



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2005/02/10


--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
On Fri, February 11, 2005 16:51, Edwin Barendse said:
[snip]
> The problem I run into is with Samba (3.0.9-r1 as well 3.0.10) it
> compiles well (fails on smbtorture, but ok) runs fine and seems oke but
> when trying to place a file on the fileshare ,for a windows client, it
> fails warning about the network name no longer available, still creates
> an empty file, when looking in the log file it states a INTERNAL ERROR
> Signal 11 and stating it should be submitted as a bug, but with the same
> system running on a dual-xeon no problem.

You mean like this (from /var/log/messages):

Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(36)
Feb 12 13:15:40 alf smbd[11608]:
===============================================================
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(37)
Feb 12 13:15:40 alf smbd[11608]: INTERNAL ERROR: Signal 11 in pid 11608
(3.0.2a)
Feb 12 13:15:40 alf smbd[11608]: Please read the appendix Bugs of the
Samba HOWTO collection
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/fault.c:fault_report(39)
Feb 12 13:15:40 alf smbd[11608]:
===============================================================
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/util.c:smb_panic(1400)
Feb 12 13:15:40 alf smbd[11608]: PANIC: internal error
Feb 12 13:15:40 alf smbd[11608]: [2005/02/12 13:15:40, 0]
lib/util.c:smb_panic(1408)
Feb 12 13:15:40 alf smbd[11608]: BACKTRACE: 0 stack frames:
Feb 12 13:15:40 alf smbd[11608]:

As you can probably tell from the above, I have the same problem on my
XLT-300... One way in which the problem manifests itself is when I try to
create a new folder on the Samba share from a Windows 2000 machine (I did
this to get the log messages shown above). W2k complains about "New
Folder" already existing, which is not true; it creates a directory named
"New Folder" and does not give me the chance to specify a name. Copying
files using ctrl-C/ctrl-V also does not work properly, but using
drag-and-drop does work. Strange...

This is for samba-3.0.2a-r2, I'll try to upgrade to a newer version
although I fear the problem will not go away (as Edwin did try with a
newer version).

BTW, my entire setup was built with CFLAGS="-mcpu=ev5 -mieee -O2 -pipe"

Marnix.


--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
I think you could attach to the samba process with gdb
and then when the segfault occured, gdb should catch
it. Of course unless you have a bit of programming
experience and know how to debug a little, none of
that is going to help much anyway.

I would try looking at this if I could, but I am
almost out of disk space on my box at the moment. I
don't think I have enough room to emerge samba right
now.

Jeff

--- Jean-Sébastien Guay <jean_seb@videotron.ca> wrote:

> Hi Jeff,
>
> In my case, here's the relevant part of my make.conf
> :
>
> CFLAGS="-mieee -O2 -mcpu=ev56 -pipe"
> CHOST="alphaev56-unknown-linux-gnu"
> CXXFLAGS="${CFLAGS}"
> MAKEOPTS="-j2"
>
> I think that's relatively conservative.
>
> Other than that, how do I get a core file? I assume
> there's something I
> need to enable so that programs will dump core when
> a segfault occurs,
> but I don't know what. But other than providing a
> core file and
> answering questions about my config, there isn't
> much I can do to zero
> in on the problem since I don't know how to use gdb
> (to get anything
> meaningful, in any case...)
>
> Thanks for your help,
>
> J-S
>
> --
> ___________________________________________
> Jean-Sébastien Guay jean_seb@videotron.ca
> http://whitestar02.webhop.org/
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.8.7 - Release
> Date: 2005/02/10
>
>
> --
> gentoo-alpha@gentoo.org mailing list
>
>




__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com



--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
Hi every one,

sorry for the delay, had other priorities, but when i attach gdb to smbd
I get the following:

<interruption !!!!!>
Seems to me a glibc problem, recompiled glibc with CFLAGS="-mcpu=ev4
-pipe" (previous "-mcpu=ev56 -O3 -pipe") no more problems!!!!!
fast conclusion, no -O3 but -O2 in your make.conf and recompile glibc
(glibc-2.3.2-r12)
<------------->

<last end of ps command output>--------------------------------------
nobody 26107 0.6 1.4 11400 4736 ? S 19:04
0:00 /usr/sbin/smbd -D
root 26108 0.0 0.4 3840 1272 pts/0 R+ 19:07 0:00 ps aux
alpha root # gdb smdb 26107
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "alpha-unknown-linux-gnu"...smdb: No such
file or directory.

Attaching to process 26107
Reading symbols from /usr/sbin/smbd...(no debugging symbols
found)...done.
Using host libthread_db library "/lib/libthread_db.so.1".
Reading symbols from /usr/lib/libldap.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libldap.so.2
Reading symbols from /usr/lib/liblber.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/liblber.so.2
Reading symbols from /usr/lib/libcups.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcups.so.2
Reading symbols from /usr/lib/libssl.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.7
Reading symbols from /usr/lib/libcrypto.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /lib/libnsl.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnsl.so.1.1
Reading symbols from /lib/libcrypt.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libcrypt.so.1.1
Reading symbols from /lib/libpam.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/libresolv.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libresolv.so.2.1
Reading symbols from /lib/libdl.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libdl.so.2.1
Reading symbols from /usr/lib/libpopt.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libpopt.so.0
Reading symbols from /lib/libc.so.6.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/gconv/UTF-16.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/UTF-16.so
Reading symbols from /usr/lib/gconv/IBM850.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/IBM850.so
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_nis.so.2
0x0000020000497f88 in select () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIG37, Real-time event 37.
0x0000020000490618 in open64 () from /lib/libc.so.6.1
(gdb)

with syslog entry:
-------------------------------------------------------------------------
Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
lib/fault.c:fault_report(36)
Mar 7 19:11:22 alpha smbd[26107]:
===============================================================
Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
lib/fault.c:fault_report(37)
Mar 7 19:11:22 alpha smbd[26107]: INTERNAL ERROR: Signal 11 in pid
26107 (3.0.10)
Mar 7 19:11:22 alpha smbd[26107]: Please read the appendix Bugs of
the Samba HOWTO collection
Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
lib/fault.c:fault_report(39)
Mar 7 19:11:22 alpha smbd[26107]:
===============================================================
Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
lib/util.c:smb_panic2(1482)
Mar 7 19:11:22 alpha smbd[26107]: PANIC: internal error
Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
lib/util.c:smb_panic2(1490)
Mar 7 19:11:22 alpha smbd[26107]: BACKTRACE: 0 stack frames:
Mar 7 19:11:22 alpha smbd[26107]:

--------------------------------------------------------------------------

was trying to move/copy a file on a windowsXP system from local drive to
the network drive.

Hopefully It gives some more inside into the problem.

With regards,

Edwin.


On Sat, 2005-02-12 at 11:37 -0800, Jeff Donsbach wrote:
> I think you could attach to the samba process with gdb
> and then when the segfault occured, gdb should catch
> it. Of course unless you have a bit of programming
> experience and know how to debug a little, none of
> that is going to help much anyway.
>
> I would try looking at this if I could, but I am
> almost out of disk space on my box at the moment. I
> don't think I have enough room to emerge samba right
> now.
>
> Jeff
>
> --- Jean-Sbastien Guay <jean_seb@videotron.ca> wrote:
>
> > Hi Jeff,
> >
> > In my case, here's the relevant part of my make.conf
> > :
> >
> > CFLAGS="-mieee -O2 -mcpu=ev56 -pipe"
> > CHOST="alphaev56-unknown-linux-gnu"
> > CXXFLAGS="${CFLAGS}"
> > MAKEOPTS="-j2"
> >
> > I think that's relatively conservative.
> >
> > Other than that, how do I get a core file? I assume
> > there's something I
> > need to enable so that programs will dump core when
> > a segfault occurs,
> > but I don't know what. But other than providing a
> > core file and
> > answering questions about my config, there isn't
> > much I can do to zero
> > in on the problem since I don't know how to use gdb
> > (to get anything
> > meaningful, in any case...)
> >
> > Thanks for your help,
> >
> > J-S
> >
> > --
> > ___________________________________________
> > Jean-Sbastien Guay jean_seb@videotron.ca
> > http://whitestar02.webhop.org/
> >
> >
> >
> > --
> > No virus found in this outgoing message.
> > Checked by AVG Anti-Virus.
> > Version: 7.0.300 / Virus Database: 265.8.7 - Release
> > Date: 2005/02/10
> >
> >
> > --
> > gentoo-alpha@gentoo.org mailing list
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
>
> --
> gentoo-alpha@gentoo.org mailing list
>


--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
Sorry, seems to have served the party cake too soon.

2 problems:
1. none empty file creation
2. folder creation

if you have tips on gdb tracing or tips, please respond.

currently trying to recompile samba with CFLAGS="-mcpu=ev4 -pipe" if
that does not help I will downgrade glibc.

1. ------none empty file creation---------------------
when copying/moving a file the smbd process kills it self leving a empty
file with the correctfilename and the windows client will respond with
'Cannot copy filename: The specified network name no longer available'
second attempt to overwrite the file gives no problem.
-------------------------------------------------------
alpha root # gdb smbd 30083
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "alpha-unknown-linux-gnu"...(no debugging
symbols found)...Using host libthread_db library
"/lib/libthread_db.so.1".

Attaching to program: /usr/sbin/smbd, process 30083
Reading symbols from /usr/lib/libldap.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libldap.so.2
Reading symbols from /usr/lib/liblber.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/liblber.so.2
Reading symbols from /usr/lib/libcups.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcups.so.2
Reading symbols from /usr/lib/libssl.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.7
Reading symbols from /usr/lib/libcrypto.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /lib/libnsl.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnsl.so.1.1
Reading symbols from /lib/libcrypt.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libcrypt.so.1.1
Reading symbols from /lib/libpam.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/libresolv.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libresolv.so.2.1
Reading symbols from /lib/libdl.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libdl.so.2.1
Reading symbols from /usr/lib/libpopt.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libpopt.so.0
Reading symbols from /lib/libc.so.6.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/gconv/UTF-16.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/UTF-16.so
Reading symbols from /usr/lib/gconv/IBM850.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/IBM850.so
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_nis.so.2
0x00000200004a8968 in select () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIG37, Real-time event 37.
0x00000200004a0a18 in open64 () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000200003eee24 in __open_catalog () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0x00000200003f0848 in kill () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) quit



2. -------------------- creating a folder ------------
first smbd process kill's it self (see gdb trace) but creates New Folder
so second proces makes without problem a New Folder (2)
----------------------------------------------------
alpha root # gdb smbd 1951
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "alpha-unknown-linux-gnu"...(no debugging
symbols found)...Using host libthread_db library
"/lib/libthread_db.so.1".

Attaching to program: /usr/sbin/smbd, process 1951
Reading symbols from /usr/lib/libldap.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libldap.so.2
Reading symbols from /usr/lib/liblber.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/liblber.so.2
Reading symbols from /usr/lib/libcups.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcups.so.2
Reading symbols from /usr/lib/libssl.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.7
Reading symbols from /usr/lib/libcrypto.so.0.9.7...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.7
Reading symbols from /lib/libnsl.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnsl.so.1.1
Reading symbols from /lib/libcrypt.so.1.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libcrypt.so.1.1
Reading symbols from /lib/libpam.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib/libpam.so.0
Reading symbols from /lib/libresolv.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libresolv.so.2.1
Reading symbols from /lib/libdl.so.2.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libdl.so.2.1
Reading symbols from /usr/lib/libpopt.so.0...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libpopt.so.0
Reading symbols from /lib/libc.so.6.1...(no debugging symbols
found)...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/gconv/UTF-16.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/UTF-16.so
Reading symbols from /usr/lib/gconv/IBM850.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/IBM850.so
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_compat.so.2
Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/libnss_nis.so.2
0x00000200004a8968 in select () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIG37, Real-time event 37.
0x00000200004a09f8 in mkdir () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00000200003eee70 in __open_catalog () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program received signal SIGABRT, Aborted.
0x00000200003f0848 in kill () from /lib/libc.so.6.1
(gdb) continue
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb) quit



On Mon, 2005-03-07 at 21:55 +0100, Edwin Barendse wrote:
> Hi every one,
>
> sorry for the delay, had other priorities, but when i attach gdb to smbd
> I get the following:
>
> <interruption !!!!!>
> Seems to me a glibc problem, recompiled glibc with CFLAGS="-mcpu=ev4
> -pipe" (previous "-mcpu=ev56 -O3 -pipe") no more problems!!!!!
> fast conclusion, no -O3 but -O2 in your make.conf and recompile glibc
> (glibc-2.3.2-r12)
> <------------->
>
> <last end of ps command output>--------------------------------------
> nobody 26107 0.6 1.4 11400 4736 ? S 19:04
> 0:00 /usr/sbin/smbd -D
> root 26108 0.0 0.4 3840 1272 pts/0 R+ 19:07 0:00 ps aux
> alpha root # gdb smdb 26107
> GNU gdb 6.0
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "alpha-unknown-linux-gnu"...smdb: No such
> file or directory.
>
> Attaching to process 26107
> Reading symbols from /usr/sbin/smbd...(no debugging symbols
> found)...done.
> Using host libthread_db library "/lib/libthread_db.so.1".
> Reading symbols from /usr/lib/libldap.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libldap.so.2
> Reading symbols from /usr/lib/liblber.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/liblber.so.2
> Reading symbols from /usr/lib/libcups.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libcups.so.2
> Reading symbols from /usr/lib/libssl.so.0.9.7...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libssl.so.0.9.7
> Reading symbols from /usr/lib/libcrypto.so.0.9.7...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libcrypto.so.0.9.7
> Reading symbols from /lib/libnsl.so.1.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libnsl.so.1.1
> Reading symbols from /lib/libcrypt.so.1.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libcrypt.so.1.1
> Reading symbols from /lib/libpam.so.0...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libpam.so.0
> Reading symbols from /lib/libresolv.so.2.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libresolv.so.2.1
> Reading symbols from /lib/libdl.so.2.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libdl.so.2.1
> Reading symbols from /usr/lib/libpopt.so.0...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libpopt.so.0
> Reading symbols from /lib/libc.so.6.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libc.so.6.1
> Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/ld-linux.so.2
> Reading symbols from /usr/lib/gconv/UTF-16.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/gconv/UTF-16.so
> Reading symbols from /usr/lib/gconv/IBM850.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/gconv/IBM850.so
> Reading symbols from /lib/libnss_files.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libnss_files.so.2
> Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libnss_compat.so.2
> Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib/libnss_nis.so.2
> 0x0000020000497f88 in select () from /lib/libc.so.6.1
> (gdb) continue
> Continuing.
>
> Program received signal SIG37, Real-time event 37.
> 0x0000020000490618 in open64 () from /lib/libc.so.6.1
> (gdb)
>
> with syslog entry:
> -------------------------------------------------------------------------
> Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
> lib/fault.c:fault_report(36)
> Mar 7 19:11:22 alpha smbd[26107]:
> ===============================================================
> Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
> lib/fault.c:fault_report(37)
> Mar 7 19:11:22 alpha smbd[26107]: INTERNAL ERROR: Signal 11 in pid
> 26107 (3.0.10)
> Mar 7 19:11:22 alpha smbd[26107]: Please read the appendix Bugs of
> the Samba HOWTO collection
> Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
> lib/fault.c:fault_report(39)
> Mar 7 19:11:22 alpha smbd[26107]:
> ===============================================================
> Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
> lib/util.c:smb_panic2(1482)
> Mar 7 19:11:22 alpha smbd[26107]: PANIC: internal error
> Mar 7 19:11:22 alpha smbd[26107]: [2005/03/07 19:11:22, 0]
> lib/util.c:smb_panic2(1490)
> Mar 7 19:11:22 alpha smbd[26107]: BACKTRACE: 0 stack frames:
> Mar 7 19:11:22 alpha smbd[26107]:
>
> --------------------------------------------------------------------------
>
> was trying to move/copy a file on a windowsXP system from local drive to
> the network drive.
>
> Hopefully It gives some more inside into the problem.
>
> With regards,
>
> Edwin.
>
>
> On Sat, 2005-02-12 at 11:37 -0800, Jeff Donsbach wrote:
> > I think you could attach to the samba process with gdb
> > and then when the segfault occured, gdb should catch
> > it. Of course unless you have a bit of programming
> > experience and know how to debug a little, none of
> > that is going to help much anyway.
> >
> > I would try looking at this if I could, but I am
> > almost out of disk space on my box at the moment. I
> > don't think I have enough room to emerge samba right
> > now.
> >
> > Jeff
> >
> > --- Jean-Sbastien Guay <jean_seb@videotron.ca> wrote:
> >
> > > Hi Jeff,
> > >
> > > In my case, here's the relevant part of my make.conf
> > > :
> > >
> > > CFLAGS="-mieee -O2 -mcpu=ev56 -pipe"
> > > CHOST="alphaev56-unknown-linux-gnu"
> > > CXXFLAGS="${CFLAGS}"
> > > MAKEOPTS="-j2"
> > >
> > > I think that's relatively conservative.
> > >
> > > Other than that, how do I get a core file? I assume
> > > there's something I
> > > need to enable so that programs will dump core when
> > > a segfault occurs,
> > > but I don't know what. But other than providing a
> > > core file and
> > > answering questions about my config, there isn't
> > > much I can do to zero
> > > in on the problem since I don't know how to use gdb
> > > (to get anything
> > > meaningful, in any case...)
> > >
> > > Thanks for your help,
> > >
> > > J-S
> > >
> > > --
> > > ___________________________________________
> > > Jean-Sbastien Guay jean_seb@videotron.ca
> > > http://whitestar02.webhop.org/
> > >
> > >
> > >
> > > --
> > > No virus found in this outgoing message.
> > > Checked by AVG Anti-Virus.
> > > Version: 7.0.300 / Virus Database: 265.8.7 - Release
> > > Date: 2005/02/10
> > >
> > >
> > > --
> > > gentoo-alpha@gentoo.org mailing list
> > >
> > >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Meet the all-new My Yahoo! - Try it today!
> > http://my.yahoo.com
> >
> >
> >
> > --
> > gentoo-alpha@gentoo.org mailing list
> >
>
>
> --
> gentoo-alpha@gentoo.org mailing list
>


--
gentoo-alpha@gentoo.org mailing list
Re: miata and samba3 [ In reply to ]
--- Edwin Barendse <ikke@tned.nl> wrote:
>
> currently trying to recompile samba with
> CFLAGS="-mcpu=ev4 -pipe"

That likely will not make much difference. What might
is to turn down optimization. Set it all the way to
-O0 if you really want to see. It will probably run
like molasses, but ....


> if
> that does not help I will downgrade glibc.

Actually, maybe a different gcc would help. Hard to
say whether upgrading or downgrading would be better
without knowing what the root of the problem is.






__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/

--
gentoo-alpha@gentoo.org mailing list