From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] [Ada] New GDB/MI command: -ada-tasks-info
Date: Fri, 16 Sep 2011 20:45:00 -0000 [thread overview]
Message-ID: <20110916203700.GC17681@adacore.com> (raw)
In-Reply-To: <1316201377-14830-2-git-send-email-brobecker@adacore.com>
I will re-send these patches, because I made two small errors:
- The introductory email got rejected because I messed up
on the subject
- The patch email subjects should have an RFA, and they don't.
I'd like the patches to be reviewed, so I will resent with
the proper subject.
Sorry about that.
On Fri, Sep 16, 2011 at 12:29:35PM -0700, Joel Brobecker wrote:
> This patch introduces a new GDB/MI command: -ada-tasks-info,
> which is meant to be the MI equivalent of the CLI `info tasks'
> command.
>
> This new command returns an array, with each row corresponding
> to one task. For now, the columns of the array corresponds to
> the columns displayed in the CLI output.
>
> gdb/ChangeLog:
>
> * ada-lang.h (struct inferior): Declare.
> (print_ada_task_info): Add declaration.
> * ada-tasks.c (print_ada_task_info): Make non-static.
> * mi/mi-cmds.c (mi_cmds): Add "ada-task-info".
> * mi/mi-cmds.h (mi_cmd_ada_task_info): Add declaration.
> * mi/mi-main.c: #include "ada-lang.h".
> (mi_cmd_list_features): Add "ada-task-info" to the list
> of supported features.
> (mi_cmd_ada_task_info): New function.
--
Joel
next prev parent reply other threads:[~2011-09-16 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1316201377-14830-1-git-send-email-brobecker@adacore.com>
2011-09-16 19:30 ` Joel Brobecker
2011-09-16 20:45 ` Joel Brobecker [this message]
2011-09-16 19:30 ` [PATCH 2/3] [Ada] Add field "thread-id" in -ada-task-info output Joel Brobecker
2011-09-16 20:27 ` [PATCH 3/3] [Ada/doco] Document the new -ada-task-info GDB/MI command Joel Brobecker
2011-09-17 7:02 ` Eli Zaretskii
2011-09-19 18:57 ` Joel Brobecker
2011-10-03 21:41 ` Joel Brobecker
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=20110916203700.GC17681@adacore.com \
--to=brobecker@adacore.com \
--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