Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/Ada] Implement Ada tasking support
Date: Tue, 23 Sep 2008 18:06:00 -0000	[thread overview]
Message-ID: <uskrqohzd.fsf@gnu.org> (raw)
In-Reply-To: <20080923150717.GF23372@adacore.com>

> Date: Tue, 23 Sep 2008 08:07:17 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > 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).

So it is a kind of thread on steroids?

> > 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).

We could extend the thread commands to display that additional info if
available.

Can there ever be more or less than exactly one thread per Ada task?

> 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.

I'm trying to establish whether they are irreconcilable.  If they can
live together, I'd suggest to merge them.


  reply	other threads:[~2008-09-23 18:06 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
2008-09-23 18:06     ` Eli Zaretskii [this message]
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=uskrqohzd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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