Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: Stan Shebs <stan@codesourcery.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Report available OS data types
Date: Tue, 15 Jun 2010 21:48:00 -0000	[thread overview]
Message-ID: <4C17F53C.9070103@codesourcery.com> (raw)
In-Reply-To: <4C17C928.5030907@vmware.com>

Michael Snyder wrote:
> 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.
>
> Is this checked in?  I still see:
>
>   (gdb) info os
>   Argument required.
>
> Am I misunderstanding something?  How do you get it to list
> the types available?
Not committed yet, I was giving people a chance to comment.  Apparently 
it would be good to document the new behavior. :-)

Stan


      reply	other threads:[~2010-06-15 21:48 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
2010-06-15 18:40 ` Michael Snyder
2010-06-15 21:48   ` Stan Shebs [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=4C17F53C.9070103@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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