Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Anisha Kaul <born.rebel.83@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Missing separate debuginfo for - GDB
Date: Thu, 20 Sep 2012 19:02:00 -0000	[thread overview]
Message-ID: <m3wqzoecwc.fsf@redhat.com> (raw)
In-Reply-To: <CAM1yFZ-NRbCcJ8c8QvNKLWvBva3paAAisJ_durk4=ipmzKGOpQ@mail.gmail.com>	(Anisha Kaul's message of "Thu, 20 Sep 2012 09:27:07 +0530")

On Thursday, September 20 2012, Anisha Kaul wrote:

> -----------------------------------------
> Missing separate debuginfo for /usr/lib64/kde4/plugins/imageformats/kimg_dds.so
> Try: zypper install -C
> "debuginfo(build-id)=a84a1969b9a69361b10f26814c0958717c48d671"

Have you tried running the command above?

> The system I have:
> -----------------------------------------
> linux-trra:~ # [B]cat /etc/issue && uname -a[/B]
> Welcome to openSUSE 11.4 "Celadon" - Kernel \r (\l).
> Linux linux-trra 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21
> 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux
> -----------------------------------------
>
> Question:
> What are the packages which do the trick?
> I searched Google for "debuginfo for kde4" - several links for several
> packages were shown.
> Do I have to hunt each one of them and install them separately or
> there is a one big package which I have to install?

I think this is a question specifically for openSUSE.  But AFAIK, you
will have to run the "zypper install -C ..." commands for each missing
debuginfo package.

-- 
Sergio


  reply	other threads:[~2012-09-20 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  3:57 Anisha Kaul
2012-09-20 19:02 ` Sergio Durigan Junior [this message]
2012-09-26  3:17 Anisha Kaul
2012-09-26 20:09 ` Tom Tromey

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=m3wqzoecwc.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=born.rebel.83@gmail.com \
    --cc=gdb@sourceware.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