Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kwok Cheung Yeung <kcy@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add the "-info-os" command to MI
Date: Thu, 13 Oct 2011 16:13:00 -0000	[thread overview]
Message-ID: <83wrc827lz.fsf@gnu.org> (raw)
In-Reply-To: <4E970915.8000207@codesourcery.com>

> Date: Thu, 13 Oct 2011 16:51:49 +0100
> From: Kwok Cheung Yeung <kcy@codesourcery.com>
> 
> This patch adds the "-info-os" command to MI as the counterpart to the GDB "info 
> os" command. It behaves in the same way as "info os", only the output is 
> formatted according to MI conventions. I've also added an entry in the 
> documentation.

Thanks.

>   On @sc{gnu}/Linux, the following values of INFOTYPE are valid:
> 
> -@anchor{linux info os infotypes}
> +@anchor{Linux OS information types}

I don't see these lines in today's CVS version of gdb.texinfo.  Does
your patch depend on some other patch?

Anyway, why is "info os processes" suddenly treated as a
Linux-specific command?  "info os" is supposed to be
platform-agnostic; if it is a Linux-only feature, it will be more
appropriate to call it "info linux", like "info dos" and "info w32"
that we already have.

> +The types of information available depend on the target operating
> +system.  The available types for @sc{gnu}/Linux are listed in
> +@ref{Linux OS information types}.

As I said above, the referenced section is not Linux-specific, and the
CVS version of the manual does not have any details there.  So
something (perhaps in my brain) is missing.

> +@smallexample
> +(gdb)
> +-info-os
> +^done,OSDataTable=@{nr_rows="9",nr_cols="2",hdr=[@{width="10",alignment=
> +"-1",col_name="col0",colhdr="Type"@},@{width="10",alignment="-1",col_nam
> +e="col1",colhdr="Description"@}],body=[item=@{col0="processes",col1="Lis
> +ting of all processes"@},item=@{col0="procgroups",col1="Listing of all p
> +rocess groups"@},item=@{col0="threads",col1="Listing of all threads"@},i
> +tem=@{col0="files",col1="Listing of all file descriptors"@},item=@{col0=
> +"sockets",col1="Listing of all internet-domain sockets"@},item=@{col0="s
> +hm",col1="Listing of all shared-memory regions"@},item=@{col0="semaphore
> +s",col1="Listing of all semaphores"@},item=@{col0="msg",col1="Listing of
> + all message queues"@},item=@{col0="modules",col1="Listing of all loaded
> + kernel modules"@}]@}

The lines here are broken in arbitrary places, which will look
illegible in the manual.  Please reformat the example so that the
output could be readable by humans.

Thanks.


  reply	other threads:[~2011-10-13 16:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 15:52 Kwok Cheung Yeung
2011-10-13 16:13 ` Eli Zaretskii [this message]
2011-11-23 23:37   ` Kwok Cheung Yeung
2011-12-06 18:53     ` Pedro Alves
2011-10-21 20:53 ` Tom Tromey
2011-10-27  0:24   ` Stan Shebs
2011-10-27 16:45     ` Tom Tromey
2011-11-24 23:15   ` Kwok Cheung Yeung
2011-11-25 11:56     ` Eli Zaretskii
2011-11-29 19:01     ` Tom Tromey
2011-11-29 23:18       ` Kwok Cheung Yeung
2011-11-30 14:47         ` 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=83wrc827lz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kcy@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