This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch/doc] Tweak "info inferiors" output.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]