From: Tom Tromey <tromey@redhat.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Pedro Alves" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: Re: Move the multi-forks support to the generic multi-inferiors support.
Date: Mon, 08 Jun 2009 22:43:00 -0000 [thread overview]
Message-ID: <m3ocsymjr8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA0789E524@ecamlmw720.eamcs.ericsson.se> (Marc Khouzam's message of "Sun\, 7 Jun 2009 21\:33\:57 -0400")
>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
Marc> Just a note that up to GDB 6.8, we used the output of "info threads"
Marc> in the DSF-GDB Eclipse frontend. With GDB 7.0 we moved to
Marc> "-thread-info"
Marc> So, I'm not affected by a change of output
Unfortunately both -thread-info and "info threads" just amount to a
call to print_thread_info. So, if we fix that to use a table, it will
change the MI output, IIUC.
FWIW, using a table in these situations seems superior to me, because
it allows for column headings and because it handles some of the
formatting bits (lining up columns) automatically.
So, at least IMO, code like this should prefer tables over things like
emitting sequences of spaces. If I'm missing some obvious drawback
here, please let me know, since I'd like to be informed...q
Marc> I'm not sure if you enforce CLI output backwards compatibility...
I think we definitely should not.
Tom
next prev parent reply other threads:[~2009-06-08 22:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 23:13 Pedro Alves
2009-05-31 20:46 ` Tom Tromey
2009-05-31 22:07 ` Pedro Alves
2009-05-31 22:23 ` Doug Evans
2009-06-01 15:58 ` Tom Tromey
2009-06-06 0:09 ` Tom Tromey
2009-06-06 16:06 ` Pedro Alves
2009-06-08 1:34 ` Marc Khouzam
2009-06-08 22:43 ` Tom Tromey [this message]
2009-06-08 23:22 ` Pedro Alves
2009-06-08 22:39 ` Tom Tromey
2009-06-08 23:16 ` Pedro Alves
2009-06-10 22:09 ` Tom Tromey
2009-06-10 22:13 ` Pedro Alves
2009-06-08 12:58 ` Pedro Alves
2009-06-11 19:32 ` Michael Snyder
2009-07-01 18:27 ` Pedro Alves
2009-07-01 19:16 ` Eli Zaretskii
2009-07-02 14:32 ` Pedro Alves
2009-07-02 19:00 ` Eli Zaretskii
2009-07-02 21:59 ` 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=m3ocsymjr8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=pedro@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