LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Gentoo (http://www.linuxquestions.org/questions/gentoo-87/)
-   -   Segmentation faults after system upgrade (http://www.linuxquestions.org/questions/gentoo-87/segmentation-faults-after-system-upgrade-922635/)

segmentation_fault 01-07-2012 04:41 PM

Segmentation faults after system upgrade
 
This looks really bad (for me). After running
Code:

emerge -uDv system
some programs (like mc - midnight commander) give a segmentation fault (yeap, that's my nick, ironic...), and I cannot emerge anything (emerge also fails with a segmentation fault. After some research I found out that this could be related to glibc, so here is some info:
Code:

$ /lib/libc.so.6
GNU C Library stable release version 2.13, by Roland McGrath et al.
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.5.3.
Compiled on a Linux 2.6.39 system on 2011-12-12.
Available extensions:
        C stubs add-on version 2.1.2
        crypt add-on version 2.1 by Michael Glad and others
        Gentoo patchset 8
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        Support for some architectures added on, not maintained in glibc core.
        BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

Code:

# gcc-config -l
 [1] x86_64-pc-linux-gnu-4.4.5
 [2] x86_64-pc-linux-gnu-4.5.3 *

 # eselect binutils show
x86_64-pc-linux-gnu-2.21.1

 # ls -l /lib64/ | grep libc
-rwxr-xr-x  1 root root 1592528 Dec 12 02:00 libc-2.13.so
lrwxrwxrwx  1 root root      12 Dec 12 02:01 libc.so.6 -> libc-2.13.so

 # ld --version
GNU ld (GNU Binutils) 2.21.1
Copyright 2011 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

# ls -l /lib64/ | grep ld-linux
lrwxrwxrwx  1 root root      10 Dec 12 02:01 ld-linux-x86-64.so.2 -> ld-2.13.so
lrwxrwxrwx  1 root root      22 Dec 12 02:01 ld-linux.so.2 -> ../lib32/ld-linux.so.2

emerge *anything* fails sooner or later.
Here is the output of mc run in gdb:
Code:

Reading symbols from /usr/bin/mc...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/mc
BFD: /lib64/libncursesw.so.5: invalid string offset 16779807 >= 6682 for section `.dynstr'
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7de6502 in ?? () from /lib64/ld-linux-x86-64.so.2
(gdb) backtrace
#0  0x00007ffff7de6502 in ?? () from /lib64/ld-linux-x86-64.so.2
#1  0x00007ffff7de9e3d in ?? () from /lib64/ld-linux-x86-64.so.2
#2  0x00007ffff7df0375 in ?? () from /lib64/ld-linux-x86-64.so.2
#3  0x00007ffff7769237 in _nc_mvcur_resume () from /lib64/libncursesw.so.5
#4  0x00007ffff7769d95 in newterm () from /lib64/libncursesw.so.5
#5  0x00007ffff7766692 in initscr () from /lib64/libncursesw.so.5
#6  0x000000000043009f in ?? ()
#7  0x0000000000415186 in ?? ()
#8  0x00007ffff6c9f09d in __libc_start_main () from /lib64/libc.so.6
#9  0x0000000000410459 in ?? ()
#10 0x00007fffffffe048 in ?? ()
#11 0x000000000000001c in ?? ()
#12 0x0000000000000001 in ?? ()
#13 0x00007fffffffe345 in ?? ()
#14 0x0000000000000000 in ?? ()

Any help/ideas much appreciated.
Any more info you might need let me know.

segmentation_fault 01-07-2012 06:02 PM

I am currently chrooted in my system from the latest gentoo minimal. Tryied to downgrade glibc to 2.12.2 but emerge didn't let me, saying that this is a shure way to destroy my system (I believe that). So I am re-emerging glibc and see if this does the trick (emerge seems to work ok in the chroot).

Ok, this seems to work. I don't get any segmentation faults so far. If revdep-rebuild completes (it was failing too) I will mark it as solved.

segmentation_fault 01-08-2012 01:45 PM

While I was pushing my system a bit it suddenly froze, so that raised questions about a RAM DIMM I installed a few days ago. I ran about 10 tests with memtest86 and it passed with no errors, but after removing the suspicious DIMM the system runs fine. Except that I am left with only 1GB RAM. So I'm going to mark the thread as solved.


All times are GMT -5. The time now is 07:20 AM.