From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Implement -thread-info.
Date: Sat, 08 Mar 2008 15:50:00 -0000 [thread overview]
Message-ID: <fqucjm$upe$1@ger.gmane.org> (raw)
In-Reply-To: <18371.25340.162317.39030@kahikatea.snap.net.nz>
Nick Roberts wrote:
> > --- a/gdb/mi/mi-cmds.c
> > +++ b/gdb/mi/mi-cmds.c
> > @@ -130,8 +130,7 @@ struct mi_cmd mi_cmds[] =
> > { "target-list-current-targets", { NULL, 0 }, NULL, NULL },
> > { "target-list-parameters", { NULL, 0 }, NULL, NULL },
> > { "target-select", { NULL, 0 }, mi_cmd_target_select},
> > - { "thread-info", { NULL, 0 }, NULL, NULL },
> > - { "thread-list-all-threads", { NULL, 0 }, NULL, NULL },
> > + { "thread-info", { NULL, 0 }, NULL, mi_cmd_thread_info },
> > { "thread-list-ids", { NULL, 0 }, 0, mi_cmd_thread_list_ids},
> > { "thread-select", { NULL, 0 }, 0, mi_cmd_thread_select},
> > { "trace-actions", { NULL, 0 }, NULL, NULL },
>
> I was thinking:
>
> *** mi-cmds.c.~1.30.~ 2008-01-04 10:24:35.000000000 +1300
> --- mi-cmds.c 2008-02-26 13:47:53.000000000 +1300
> *************** struct mi_cmd mi_cmds[] =
> *** 133,138 ****
> --- 133,139 ----
> { "thread-info", { NULL, 0 }, NULL, NULL },
> { "thread-list-all-threads", { NULL, 0 }, NULL, NULL },
> { "thread-list-ids", { NULL, 0 }, 0, mi_cmd_thread_list_ids},
> + { "thread-info", { "info threads", 0 }, NULL, NULL },
> { "thread-select", { NULL, 0 }, 0, mi_cmd_thread_select},
> { "trace-actions", { NULL, 0 }, NULL, NULL },
> { "trace-delete", { NULL, 0 }, NULL, NULL },
>
> like for "info break".
>
> I realise that -thread-info can give info about one thread but presumably
> the change could allow "info threads" to do that too (just as is already
> done for "info break"). Then you just need
>
> + { "thread-info", { "info threads", 1 }, NULL, NULL },
>
> WDYT?
I think I agree with Dan's concerns about using a backward-compatibility
mechanisms.
- Volodya
next prev parent reply other threads:[~2008-03-08 15:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 15:33 Vladimir Prus
2008-02-18 6:26 ` Nick Roberts
2008-02-18 7:38 ` Vladimir Prus
2008-02-18 21:45 ` Nick Roberts
2008-02-20 11:28 ` Vladimir Prus
2008-02-20 19:07 ` Eli Zaretskii
2008-02-20 19:38 ` Nick Roberts
2008-02-20 20:03 ` Vladimir Prus
2008-02-26 0:58 ` Nick Roberts
2008-02-26 1:21 ` Daniel Jacobowitz
2008-03-23 4:56 ` Nick Roberts
2008-03-23 7:38 ` Vladimir Prus
2008-03-23 16:22 ` Daniel Jacobowitz
2008-03-08 15:50 ` Vladimir Prus [this message]
2008-03-08 15:55 ` Vladimir Prus
2008-03-08 20:04 ` Nick Roberts
2008-03-10 7:59 ` Vladimir Prus
2008-03-10 9:13 ` Nick Roberts
2008-03-14 10:17 ` Vladimir Prus
2008-03-17 18:40 ` Michael Snyder
2008-03-14 15:08 ` Daniel Jacobowitz
2008-03-14 15:11 ` Daniel Jacobowitz
2008-03-14 17:04 ` Vladimir Prus
2008-03-14 18:04 ` Daniel Jacobowitz
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='fqucjm$upe$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@sources.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