From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: A target has-a 1:N threads?
Date: Thu, 09 Oct 2003 15:40:00 -0000 [thread overview]
Message-ID: <3F85817A.3040500@redhat.com> (raw)
In-Reply-To: <3F856BF9.5020708@redhat.com>
> Hello,
>
> At present GDB maintains a thread-db that contains all the "threads" known to GDB. The list is cross-target. That is, it can include both LWPs from the lower "process layer" and "threads" from the higher "thread layer".
>
> I think the currently implicit target <-> thread relationship should be made more explicit:
>
> - thread_info should point back at it's target
> - a target should let you iterate over its "threads"
>
> This, I belive, will help clean-up the current tid:pid dance. A thread would always know its target and hence thread operations would always be applied at the correct level.
Make that 0:N threads. I forgot the targets that don't have threads.
Andrew
next prev parent reply other threads:[~2003-10-09 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 14:08 Andrew Cagney
2003-10-09 15:40 ` Andrew Cagney [this message]
2003-10-09 16:10 ` Andrew Cagney
2003-10-09 19:50 ` Jim Blandy
2003-10-09 20:19 ` Paul Koning
2003-10-09 22:00 ` Andrew Cagney
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=3F85817A.3040500@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@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