From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch/doc] Tweak "info inferiors" output.
Date: Fri, 14 Aug 2009 19:27:00 -0000 [thread overview]
Message-ID: <200908142016.00060.pedro@codesourcery.com> (raw)
In-Reply-To: <8363cqjn3s.fsf@gnu.org>
On Friday 14 August 2009 18:56:23, Eli Zaretskii wrote:
> > From: Pedro Alves <pedro@codesourcery.com>
> > Date: Fri, 14 Aug 2009 16:46:00 +0100
> >
> > Eli, documentation bits ok?
>
> I have two comments:
>
> . Does "ID" and the numbers below it really fail to align, as the
> example shows? If so, perhaps we should align them.
It's a single column called "Target ID". The target can put there
whatever it wants, though "process foo" will be the most common.
E.g.,
(gdb) info inferiors
Id Target ID
* 1 process 309954
4 capsule 2342
2 process 109
3 process 56
5 foo 1234
6 remote target
This second column is very much like the second column
of "info threads", except, "info threads" doesn't have
column headers ...:
(gdb) info threads
1 Thread 0x7ffff7fd76e0 (LWP 22139) main (argc=1, argv=0x7fffffffe378) at ../../src/gdb/gdb.c:26
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The target decides what to print here.
Maybe there's a better name for the column. Some debuggers
seem to call that the system ID (although most can assume
an unix-like system). Target ID sounded more GDB-ish
to me. (it may well be it sounds implementor speak, I
dunno).
> . I'd prefer to explain what can appear under "Target".
Okay, I can do that.
--
Pedro Alves
next prev parent reply other threads:[~2009-08-14 19:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 16:22 Pedro Alves
2009-08-14 17:38 ` Tom Tromey
2009-08-14 18:30 ` Eli Zaretskii
2009-08-14 19:27 ` Pedro Alves [this message]
2009-08-14 20:59 ` Eli Zaretskii
2009-08-17 14:37 ` Pedro Alves
2009-08-17 14:45 ` Pedro Alves
2009-08-17 17:55 ` Eli Zaretskii
2009-08-17 18:01 ` Tom Tromey
2009-08-17 19:28 ` Eli Zaretskii
2009-08-17 20:12 ` Stan Shebs
2009-08-24 11:15 ` Pedro Alves
2009-08-24 18:54 ` Eli Zaretskii
2009-08-25 15:40 ` Pedro Alves
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=200908142016.00060.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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