[Crash/Linux] libc-2.21.so@0x349c8

Discussion in 'Mac and Linux' started by sevmek, August 26, 2015.

  1. sevmek

    sevmek Active Member

    Messages:
    110
    Likes Received:
    57

    Attached Files:

  2. sevmek

    sevmek Active Member

    Messages:
    110
    Likes Received:
    57
  3. crizmess

    crizmess Well-Known Member

    Messages:
    434
    Likes Received:
    317
    Hmm, 0x349c8@libc is probably an address to something generic like _libc_sigabort or _raise. :-(

    You could, just for fun, try to install the debug symbols for your libc (How to do this depends on your distribution. Google would be a good start). But I'm not sure if Ubers crash report tool supports external symbols.
  4. sevmek

    sevmek Active Member

    Messages:
    110
    Likes Received:
    57
    @ crizmess
    EDIT: Coming from Debian and using Fedora now, I got confused, the glibc-devel package is not what I need here.

    For my own reference here is the command line for Fedora 22:
    Code:
    $ su -c 'dnf debuginfo-install glibc-2.21-7.fc22.x86_64'
    ../..
    Installed :
      glibc-debuginfo.x86_64 2.21-7.fc22  
      glibc-debuginfo-common.x86_64 2.21-7.fc22
    
    We'll see how it helps. Thank you!
    Last edited: September 19, 2015
    crizmess likes this.

Share This Page