Results 1 to 5 of 5

Thread: GDB breakpoint fails, debug info for libc not available?

  1. #1

    Default GDB breakpoint fails, debug info for libc not available?

    When I debug a program with GDB and hit a break point I get:


    Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
    Try: zypper install -C "debuginfo(build-id)=2b25d8329d1aa713a2cc61b5cb701f6f89c78022"
    Missing separate debuginfo for /lib64/libm.so.6
    Try: zypper install -C "debuginfo(build-id)=f05646449077dfbf15d5f78251a3b25e0f955dd9"
    Missing separate debuginfo for /lib64/libc.so.6
    Try: zypper install -C "debuginfo(build-id)=9b674b2caef1982db55e436bca814060e1705b7f"
    When I install the suggested packages the debuginfo does not match the object files. I get:

    warning: the debug information found in "/usr/lib/debug//lib64/libc-2.11.2.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch).

    warning: the debug information found in "/usr/lib/debug/lib64/libc-2.11.2.so.debug" does not match "/lib64/libc.so.6" (CRC mismatch).

    Missing separate debuginfo for /lib64/libc.so.6
    Try: zypper install -C "debuginfo(build-id)=9b674b2caef1982db55e436bca814060e1705b7f"
    The last package is not found. Is this missing from the repositories?

    Why is there a CRC mismatch?

  2. #2
    Join Date
    Dec 2010
    Location
    Belgium, Europe
    Posts
    192

    Default Re: GDB breakpoint fails, debug info for libc not available?

    I'm having the same problem. *bump*

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: GDB breakpoint fails, debug info for libc not available?

    On 02/28/2011 09:06 AM, pdedecker wrote:
    >
    > I'm having the same problem. *bump*


    maybe the first poster (and you) might have a better chance if this
    were in the forum here where programmers hang out:
    http://forums.opensuse.org/english/o...ing-scripting/

    and, if you post to there you might find a quicker response if you
    include more information, like:

    -operating system and version you are using

    -desktop environment and version you are using

    -the version of GDB you are using

    -what steps you have taken which were unsuccessful in resolving the
    problem (so none tell you to try something you already have tried)..

    -were any of the hits from this google helpful?
    http://tinyurl.com/6472s5x

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

  4. #4
    Join Date
    Dec 2010
    Location
    Belgium, Europe
    Posts
    192

    Default Re: GDB breakpoint fails, debug info for libc not available?

    I added this repo, then I did zypper in glibc-debuginfo. This solves the issue.

  5. #5
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: GDB breakpoint fails, debug info for libc not available?

    On 02/28/2011 02:36 PM, pdedecker wrote:

    > I added 'this repo' (http://download.opensuse.org/debug/update/11.3/),
    > then I did -zypper in glibc-debuginfo-. This solves the issue.


    GREAT! happy you [solved] it!!

    and, more happy you were kind enough to return here and leave the
    solution, for the next who follows the trail to here!!

    --
    DenverD
    CAVEAT: http://is.gd/bpoMD
    [NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
    173.14.28 3D, Athlon 64 3000+]
    "It is far easier to read, understand and follow the instructions than
    to undo the problems caused by not." DD 23 Jan 11

Tags for this Thread

Posting Permissions

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