Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: assert that target_fetch_registers did its job
Date: Sat, 07 Aug 2004 18:54:00 -0000	[thread overview]
Message-ID: <41152560.1020700@gnu.org> (raw)
In-Reply-To: <20040807184215.GA21818@nevyn.them.org>


> Is there even a thread/lwp separation in GDB core?  My understanding
> was that the core should never see anything having to do with an LWP;
> at least the trivial LWP == thread mapping should have taken place
> somewhere, and GDB should just talk to the threads.

In theory, yes.  In reality, look at regcache.c :-(

Andrew



  reply	other threads:[~2004-08-07 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 23:00 Jim Blandy
2004-07-24  0:45 ` Daniel Jacobowitz
2004-08-03 14:23   ` Andrew Cagney
2004-08-07 18:42     ` Daniel Jacobowitz
2004-08-07 18:54       ` Andrew Cagney [this message]
2004-08-04 17:51   ` Jim Blandy
2004-08-06 20:50 ` Nathan J. Williams
2004-08-06 23:43   ` Jim Blandy
2004-08-07  1:47     ` Ian Lance Taylor
2004-08-07 16:13       ` Andrew Cagney
2004-08-07 18:31         ` Jim Blandy

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=41152560.1020700@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@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