Find the answer to your Linux question:
Results 1 to 4 of 4
a while back i had a similar problem with mdk8.2, so i went out and got mdk9, its pretty much standard out of the box install, except wine wasnt happy ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Engineer
    Join Date
    Dec 2002
    Location
    New Zealand
    Posts
    766

    upgraded glibc and now rpm doesnt work


    a while back i had a similar problem with mdk8.2, so i went out and got mdk9, its pretty much standard out of the box install, except wine wasnt happy and to install the latest version i needed glibc-2.3.x

    my system WAS working fine, then i installed

    glibc-2.3.2-2mdk
    glibc-devel-2.3.2-2mdk
    ifplugd-0.13-3mdk
    initscripts-7.06-11mdk
    locales-2.3.2-1mdk
    locales-en-2.3.2-1mdk

    all of which were necescary to install glibc-2.3.2, now rpm segfaults everytime i try to install anything

  2. #2
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Do you know how to use gdb? If so, do the same in gdb and post the backtrace when the segfault occurs. If you don't know how, start gdb and use these commands (replace args with the actual arguments to pass to rpm):
    Code:
    file /bin/rpm
    set args <args>
    run
    Then wait until the segfault occurs, and run "bt" (for backtrace). When you're done, run "quit" to exit gdb.

  3. #3
    Linux Engineer
    Join Date
    Dec 2002
    Location
    New Zealand
    Posts
    766
    Code:
    &#40;gdb&#41; file /bin/rpm
    Reading symbols from /bin/rpm...&#40;no debugging symbols found&#41;...done
    &#40;gdb&#41; set args -Uivh /home/myself/tbi/*
    &#40;gdb&#41; run
    Starting program&#58; /bin/rpm -Uivh /home/myself/tbi/*
    warning shared library handler failed to enable breakpoint
    Preparing...                 ########################################## &#91;100%&#93;
    
    Program received signal SIGSEGV, Segmentation fault.
    0x081b488a in ?? &#40;&#41;
    &#40;gdb&#41; bt
    #0  0x081b488a in ?? &#40;&#41;
    #1  0x081b4b1c in ?? &#40;&#41;
    #2  0x081b4ca2 in ?? &#40;&#41;
    #3  0x081ae420 in ?? &#40;&#41;
    #4  0x0819165c in ?? &#40;&#41;
    #5  0x081adecb in ?? &#40;&#41;
    #6  0x08192266 in ?? &#40;&#41;
    #7  0x0819165c in ?? &#40;&#41;
    #8  0x08192157 in ?? &#40;&#41;
    #9  0x08184d49 in ?? &#40;&#41;
    #10 0x0818541b in ?? &#40;&#41;
    #11 0x08169f7e in ?? &#40;&#41;
    #12 0x08169add in ?? &#40;&#41;
    #13 0x08067722 in ?? &#40;&#41;
    #14 0x0806678a in ?? &#40;&#41;
    #15 0x080675c2 in ?? &#40;&#41;
    #16 0x08076bca in ?? &#40;&#41;
    #17 0x0806ba59 in ?? &#40;&#41;
    #18 0x08048fb2 in ?? &#40;&#41;
    #19 0x081433fa in ?? &#40;&#41;
    &#40;gdb&#41; quit
    im guessing the line that says shared library handler failed... refers to glibc? maybe my glibc-2.3.2 dload is corrupt or something.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    No, there doesn't seem to anything wrong with your glibc. All those addresses are within the rpm binary mapping. glibc is usually mapped somewhere above 0x40000000. It's a pity that the rpm is normally stripped, so that there's no symbolic info. Try downloading the latest version from www.rpm.org and see if that works better.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •