Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>,
	       nt_mahmood@yahoo.com, Debug List <debug-list@redhat.com>
Subject: Re: [debug-list] Missing separate debuginfos
Date: Fri, 15 Mar 2013 15:29:00 -0000	[thread overview]
Message-ID: <20130315152926.GA28676@host2.jankratochvil.net> (raw)
In-Reply-To: <874ngc3crt.fsf@fleche.redhat.com>

On Fri, 15 Mar 2013 16:26:14 +0100, Tom Tromey wrote:
> Maybe it would be nice if debuginfo-install were a gdb command.

It should be a question installing it on its own if answered 'y', according to
some feedback in the meantime.

And it should run some PackageKit or even apt-get etc. depending on the OS.


Jan


      reply	other threads:[~2013-03-15 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 17:46 Mahmood Naderan
2013-02-19 20:14 ` Sergio Durigan Junior
2013-02-19 20:36   ` Pedro Alves
2013-03-15 15:26     ` Tom Tromey
2013-03-15 15:29       ` Jan Kratochvil [this message]

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=20130315152926.GA28676@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=debug-list@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=nt_mahmood@yahoo.com \
    --cc=palves@redhat.com \
    --cc=tromey@redhat.com \
    /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