From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Target-specific thread switching backend
Date: Wed, 05 Dec 2007 18:37:00 -0000 [thread overview]
Message-ID: <20071205160748.GA24295@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0712051506590.26738@perivale.mips.com>
On Wed, Dec 05, 2007 at 03:22:34PM +0000, Maciej W. Rozycki wrote:
> It sounds worrying though, that the notion of the current thread within
> GDB is changed freely somewhere when there is a dedicated call to switch
> threads, hmm...
Yes, especially when all the thread IDs should be really be arguments
to these functions. For instance, the global current_regcache is
silly; we should support more than one regcache live at a time.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-12-05 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 14:26 Maciej W. Rozycki
2007-12-05 15:22 ` Daniel Jacobowitz
2007-12-05 16:07 ` Maciej W. Rozycki
2007-12-05 18:37 ` Daniel Jacobowitz [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=20071205160748.GA24295@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.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