From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: What to do with threads?
Date: Sun, 02 Feb 2003 21:04:00 -0000 [thread overview]
Message-ID: <3E3D87B5.9080306@redhat.com> (raw)
Hello,
To put it simply, how can one fix this:
static CORE_ADDR
d10v_read_pc (ptid_t ptid)
{
....
read_register (PC_REGNUM);
....
}
There are problems at many levels. Off the top of my head:
- ptid can identify a thread and/or a LWP
- there sometimes isn't even a thread and/or a LWP
- the selected and current thread both fight over the same global data
structures
- long long term, an objective is to have gdb debug multiple processes /
ISAs
- so long term that it is probably funny, an objective is to have gdb
debugging multiple targets
I think we've fought the frame battle and won (the casualties will take
ages to recover mind :-), the thread battle, I think, is next.
Andrew
next reply other threads:[~2003-02-02 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 21:04 Andrew Cagney [this message]
2003-02-03 16:58 ` Quality Quorum
2003-03-03 23:40 ` Andrew Cagney
2003-03-04 2:59 ` Daniel Jacobowitz
2003-03-04 14:35 ` 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=3E3D87B5.9080306@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