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/Ada] Implement Ada tasking support
Date: Tue, 23 Sep 2008 15:07:00 -0000	[thread overview]
Message-ID: <20080923150717.GF23372@adacore.com> (raw)
In-Reply-To: <uwsh3o8g6.fsf@gnu.org>

Hi Eli,

> What is the differences, if any, between threads Ada tasks?

An Ada task carries with it a lot of semantic information thanks
to the Ada Task Control Block (the ATCB). The ATCB contains exactly
one entry per task created, and we can determine from this entry
some information such as the task name, the task state (is is running,
stuck on a rendez-vous, waiting for a rendez-vous, terminated, etc),
or who is the parent, etc. We can also use the debugging information
to extract more information such as the list of entries for instance
(these are routines in the task that you can call to perform a
rendez-vous).  But we haven't tried to take advantage of that, at
least not yet.

> Would it make sense to make the existing threads commands to refer to
> Ada tasks, instead of introducing a whole new bunch of commands?

I don't think so, because I think that Ada tasks and threads are
quite different, and the information displayed for these tasks
has some language-specific parts to it (task state, for instance).
On the other hand, I see the "thread" support as a layer that
provides information that is language-neutral, but closer to
the underlying system. Both group of commands serve, IMO, a slightly
different purpose.

> Finally, if we do decide to have these new task commands, are there
> any other languages which could, at least in principle, benefit from
> the same feature for similar reasons, or is Ada the only one?

I'm not sure - I don't know the other languages all that well.

-- 
Joel


  reply	other threads:[~2008-09-23 15:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 23:33 Joel Brobecker
2008-09-23  3:20 ` Eli Zaretskii
2008-09-23 15:07   ` Joel Brobecker [this message]
2008-09-23 18:06     ` Eli Zaretskii
2008-09-23 18:30       ` Joel Brobecker
2008-09-23 19:17         ` Eli Zaretskii
2008-09-23 19:00     ` Tom Tromey
2008-09-23 18:24 ` Eli Zaretskii
2008-09-23 19:22 ` Tom Tromey

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=20080923150717.GF23372@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