From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: A target has-a 1:N threads?
Date: Thu, 09 Oct 2003 22:00:00 -0000 [thread overview]
Message-ID: <3F85DA77.3080108@redhat.com> (raw)
In-Reply-To: <vt2n0cab39h.fsf@zenia.home>
> Sure --- every thread should know how to read and write its registers,
> so it needs to know which target to use for that.
> I'm more concerned about the symbol table's ability to support
> multiple processes, the solib list handling, and so on. There needs
> to be a data structure that represents an address space, with which we
> can associate the addr->block, addr->line, and addr->symbol mappings,
> the solib lists, and so on.
Fortunatly, the change of making the 0:N target has-a thread
relationship explicit isn't directly dependant on other changes. That
lets me delay worrying about your problem until a later date (and
perhaphs by then you will have worred it into a solution :-)
enjoy,
Andrew
prev parent reply other threads:[~2003-10-09 22:00 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
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 [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=3F85DA77.3080108@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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