Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have started getting mail titled "Segfault in Samba", containing the following, but Samba seems functional.... Anyone have a quick notion as to cause? I have a simple 3 computer network using a linksys router, one Debian server (etch), one debian desktop (etch) and one winXP computer.
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for pid 4091 (/usr/sbin/winbindd).
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred.
If the problem persists, you are encouraged to first install the
samba-dbg package which contains the debugging symbols for samba
binaries. Then submit the provided information as a bug report to Debian.
For information about the procedure for submitting bug reports , please see http://www.debian.org/Bugs/Reporting or the reportbug(1) manpage.
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1480661312 (LWP 4091)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xa7d8f7be in waitpid () from /lib/tls/libc.so.6
#0 0xa7d8f7be in waitpid () from /lib/tls/libc.so.6
#1 0xa7d37699 in strtold_l () from /lib/tls/libc.so.6
#2 0x080e7207 in smb_panic2 ()
#3 0x080e733a in smb_panic ()
#4 0x0807b81c in init_domain_list ()
#5 0x08074a22 in main ()
Hi, I think you will need to recompile an unstripped glibc & glibc-solibs (according to my slack machine) in order to get more debugging symbols. All debug symbols are usually required in order to properly debug a problem. It may be very difficult but worth the trouble if you manage to do it.
edit: also, check the samba bug report list to see if it has already beed identified and solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.