From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Pedro Alves" <pedro@codesourcery.com>, "Tom Tromey" <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: Move the multi-forks support to the generic multi-inferiors support.
Date: Mon, 08 Jun 2009 01:34:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA0789E524@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <200906061707.21594.pedro@codesourcery.com>
> -----Original Message-----
> From: gdb-patches-owner@sourceware.org
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Pedro Alves
> Sent: June-06-09 12:07 PM
> To: Tom Tromey
> Cc: gdb-patches@sourceware.org
> Subject: Re: Move the multi-forks support to the generic
> multi-inferiors support.
>
> On Saturday 06 June 2009 01:07:29, Tom Tromey wrote:
>
> > How about this? It adds the column headings and prints
> something when
> > there are no inferiors.
>
> This is fine with me, thanks, but,
>
> are you planning on doing something similar to "info threads" output?
> IMO, both these commands should be consistent. In that case, you
> may have an issue with MI, as it calls print_thread_info --- I don't
> know if using a table instead of a list changes MI output.
Just a note that up to GDB 6.8, we used the output of "info threads"
in the DSF-GDB Eclipse frontend. With GDB 7.0 we moved to
"-thread-info"
So, I'm not affected by a change of output, but
I'm saying this to point out that some frontend may still be using
it and may break when moving to GDB 7.0 if the format changes.
I think CDI-GDB (the older Eclipse GDB frontend) is in that
category.
I'm not sure if you enforce CLI output backwards compatibility...
Marc
>
> (I was a bit surprised to (re-)find that MI doesn't use
> print_inferior)
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2009-06-08 1:34 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 [this message]
2009-06-08 22:43 ` Tom Tromey
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=6D19CA8D71C89C43A057926FE0D4ADAA0789E524@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.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