From: Daniel Jacobowitz <dan@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Report available OS data types
Date: Tue, 15 Jun 2010 13:51:00 -0000 [thread overview]
Message-ID: <20100615135124.GA32295@caradoc.them.org> (raw)
In-Reply-To: <4C16BCB9.5040106@codesourcery.com>
On Mon, Jun 14, 2010 at 04:35:21PM -0700, Stan Shebs wrote:
> As a lead-in to some upcoming work on "OS awareness" for Linux GDB,
> here is a little patch for "info os" to return the types of data
> available (which is currently just "processes"), instead of erroring
> out.
>
> Stan
>
> 2010-06-14 Stan Shebs <stan@codesourcery.com>
>
> * osdata.c (get_osdata): Warn separately if target does not report
> type list.
> (info_osdata_command): Allow empty type, report error if target
> does not return available types of OS data.
> * linux-nat.c (linux_nat_xfer_osdata): Report list of OS data
> types if no annex supplied.
Doesn't something in this patch need a doc update?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-06-15 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 23:35 Stan Shebs
2010-06-15 13:51 ` Daniel Jacobowitz [this message]
2010-06-15 18:40 ` Michael Snyder
2010-06-15 21:48 ` Stan Shebs
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=20100615135124.GA32295@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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