public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Cernansky <hslists2@zoznam.sk>
To: gentoo-user@lists.gentoo.org
Subject: Re[2]: [gentoo-user] Samba crashes after upgrading system
Date: Sun, 17 Jul 2005 17:59:42 +0200 (CEST)	[thread overview]
Message-ID: <Mahogany-0.66.0-13091-20050717-175942.00@kihnet.sk> (raw)
In-Reply-To: <42D97F2A.1080300@asmallpond.org>

On Sat, 16 Jul 2005 23:42:02 +0200 Richard Fish <bigfish@asmallpond.org> wrote:

RF> Zac Medico wrote:
RF> >
RF> > In that case I would just rebuild the current version without 
RF> > -ftracer.  In the future use quickpkg or FEATURES=buildpkg to give 
RF> > yourself a roll back plan.  AFAICT downgrading glibc should not be 
RF> > much of an issue in itself because the API is still the same and it 
RF> > would just take you back where you were before.
RF> 
RF> For a complete list of packages that should be rebuilt, you can run:
RF> 
RF> equery belongs `ldd /usr/sbin/smbd  | grep ' /' | awk '{print $3}'` | 
RF> sort | uniq
RF> 
RF> This will print the name of every package that contains a library that 
RF> smbd depends upon.
RF> 
RF> I would not rebuild the entire system at this point, but if -ftracer 
RF> does turn out to be the source of your problem, then a rebuild should 
RF> scheduled soon!

Well, ldd shows that smbtree depends on popt and glibc. According to gdb,
the problem seems to be in glibc (/usr/lib64/gconv/IBM852.so belongs to
glibc):

$ gdb smbtree
[snip]
(gdb) r
Starting program: /usr/bin/smbtree 
(no debugging symbols found)
(no debugging symbols found)
[snip]
Program received signal SIGSEGV, Segmentation fault.
0x00002aaaab4459bc in gconv () from /usr/lib64/gconv/IBM852.so
(gdb) bt
#0  0x00002aaaab4459bc in gconv () from /usr/lib64/gconv/IBM852.so
#1  0x00002aaaab23efa2 in gconv () from /usr/lib64/gconv/UTF-16.so
#2  0x00002aaaab034f78 in iconv_close () from /lib/libc.so.6
#3  0x00002aaaab03456b in iconv () from /lib/libc.so.6
#4  0x00000000004416b0 in smb_register_charset ()
#5  0x00000000004417db in smb_iconv ()
#6  0x00000000004222fa in lazy_initialize_conv ()
#7  0x000000000042283b in convert_string ()
#8  0x0000000000432308 in init_doschar_table ()
#9  0x00000000004221c4 in init_iconv ()
#10 0x000000000041c9e4 in lp_file_list_changed ()
#11 0x000000000041dfc5 in lp_do_parameter ()
#12 0x000000000042085a in set_store_dos_attributes ()
#13 0x0000000000420b98 in pm_process ()
#14 0x000000000041f83b in lp_load ()
#15 0x0000000000418c68 in main ()

So I decide to downgrade glibc first, but it did not help. Then I downgrade
linux-headers and re-emerge (downgraded) glibc and samba (for sure). Again
without success. :-( I removed -ftracer at first of course.

I'm stuck now. I don't believe that rebuild of whole system (without
-ftracer) fixes the problem because /usr/lib64/gconv/IBM852.so depends only
on libraries from glibc.

$ ldd /usr/lib64/gconv/IBM852.so
        libc.so.6 => /lib/libc.so.6 (0x00002aaaaabce000)
        /lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
$ ldd /lib/libc.so.6
        /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
$ ldd /lib64/ld-linux-x86-64.so.2
        statically linked

What do you think?

Robert


-- 
Robert Cernansky
E-mail: hslists2@zoznam.sk
Jabber: HS@jabber.sk

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-17 16:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-15 22:24 [gentoo-user] Samba crashes after upgrading system Robert Cernansky
2005-07-16 18:03 ` Zac Medico
2005-07-16 19:33   ` Re[2]: " Robert Cernansky
2005-07-16 19:49     ` Richard Fish
2005-07-16 20:48       ` Re[2]: " Robert Cernansky
2005-07-16 20:59         ` Zac Medico
2005-07-16 19:58     ` Zac Medico
2005-07-16 20:57       ` Re[2]: " Robert Cernansky
2005-07-16 21:08         ` Zac Medico
2005-07-16 21:42           ` Richard Fish
2005-07-17 15:59             ` Robert Cernansky [this message]
2005-07-17 17:45               ` Zac Medico
2005-07-17 18:50                 ` Re[2]: " Robert Cernansky
2005-07-17 19:02                   ` Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Mahogany-0.66.0-13091-20050717-175942.00@kihnet.sk \
    --to=hslists2@zoznam.sk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox