From: Andrew Cagney <ac131313@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Re-initializing a list after the control returns to gdb...
Date: Wed, 19 Feb 2003 16:49:00 -0000 [thread overview]
Message-ID: <3E53B6B3.6010409@redhat.com> (raw)
In-Reply-To: <20030219160523.GM2105@gnat.com>
>> A more higher level question. What exactly is the story behind
>> ada-task*. I glanced at the code and it looked very like a clone of the
>> existing thread code.
>
>
> Not quite: What happens is that the GNAT runtime maintains an array
> of Ada_Task_Control_Block. The ada-tasks module reads this array
> to build the list of tasks, and display the status information for
> each task. We then try to use the thread module to do the task
> switching.
So let me get my head round this, the target stack should look like:
ada-tasks
threads
lwp
proc/ptrace
or possibly the ada-tasks sits more beside the thread code?
Andrew
> (We realize the code is a bit horrible, that's why we are trying to
> clean it up a bit. The question I asked was in fact for one of these
> cleanups. I can send my latest WIP version if yo are interested in
> the current state of this file).
No, I just know it needs that cleanup.
Andrew
next prev parent reply other threads:[~2003-02-19 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 2:01 Joel Brobecker
2003-02-19 12:47 ` Andrew Cagney
2003-02-19 16:05 ` Joel Brobecker
2003-02-19 16:49 ` Andrew Cagney [this message]
2003-02-19 17:46 ` Joel Brobecker
2003-02-19 17:01 ` Andrew Cagney
2003-02-19 17:50 ` Joel Brobecker
2003-02-19 18:05 ` Andrew Cagney
2003-02-19 19:24 ` Joel Brobecker
2003-02-19 20:30 ` Andrew Cagney
2003-02-25 1:37 ` Joel Brobecker
2003-02-26 15:57 ` Andrew Cagney
2003-02-27 7:13 ` Joel Brobecker
2003-02-27 18:44 ` Andrew Cagney
2003-02-28 7:42 ` 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=3E53B6B3.6010409@redhat.com \
--to=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--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