Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/NEWS] Mention new feature "Ada tasking support"
Date: Wed, 22 Oct 2008 22:15:00 -0000	[thread overview]
Message-ID: <20081022221456.GI3638@adacore.com> (raw)
In-Reply-To: <uljwge3o2.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

> Fine, but then may I suggest
> 
>    info task N
>      Print detailed information about task number N.
> 
> (and similar change in "task TASK_NO")?

I like it! Checked in as attached.

Thanks, Eli.
-- 
Joel

[-- Attachment #2: NEWS-ada-tasks.diff --]
[-- Type: text/plain, Size: 887 bytes --]

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.291
diff -u -p -r1.291 NEWS
--- NEWS	20 Oct 2008 16:18:59 -0000	1.291
+++ NEWS	22 Oct 2008 22:13:09 -0000
@@ -90,6 +90,20 @@ are treated as the standard definitions,
   GDB now has support for scripting using Python.  Whether this is
   available is determined at configure time.
 
+* Ada tasking support
+
+  Ada tasks can now be inspected in GDB. The following commands have
+  been introduced:
+
+    info tasks
+      Print the list of Ada tasks.
+    info task N
+      Print detailed information about task number N.
+    task
+      Print the task number of the current task.
+    task N
+      Switch the context of debugging to task number N.
+
 * New commands
 
 find [/size-char] [/max-count] start-address, end-address|+search-space-size,

      reply	other threads:[~2008-10-22 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 19:57 Joel Brobecker
2008-10-22 20:16 ` Eli Zaretskii
2008-10-22 20:18   ` Joel Brobecker
2008-10-22 21:11     ` Eli Zaretskii
2008-10-22 22:15       ` Joel Brobecker [this message]

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=20081022221456.GI3638@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --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