Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: msnyder@redhat.com
Cc: kettenis@science.uva.nl, gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Make Linux use the new unified x86 watchpoint support
Date: Tue, 27 Mar 2001 09:46:00 -0000	[thread overview]
Message-ID: <200103271746.MAA08374@indy.delorie.com> (raw)
In-Reply-To: <3AC0C5B6.3C05@redhat.com>

> Date: Tue, 27 Mar 2001 08:54:14 -0800
> From: Michael Snyder <msnyder@redhat.com>
> 
> > >    This possibility has been discussed back in November, but the
> > >    conclusion was that it's not a good idea.  I don't remember the
> > >    details, but the reasons had something to do with threads and how
> > >    the register cache is used in conjunction with threads.  (I can dig
> > >    out the URLs of the relevant messages, if you want to read them.)
> > >
> > > I suggested doing this, but several people objected to exposing the
> > > debug registers in this way.  Threads have nothing to do with it
> > 
> > I'm quite sure they did.  IIRC, the issue was that debug registers are
> > global, whereas normal registers are per thread.
> 
> Mmmmm... that's probably true.  However the effect would just be
> that all threads appear to have the same values for debug regs.
> If you change them in one, they'll change in all.

As far as I understood, GDB's regcache cannot do such magic.  It
assumes that all the registers are per thread, so if you change them
in one thread, the other threads' registers remain unchanged in the
cache.

In other words, this kind of global registers is (or was when we
discussed it) incompatible with how regcache works.  That is why I was
advised not to introduce the debug registers into the regcache.


  reply	other threads:[~2001-03-27  9:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 18:47 Mark Kettenis
2001-03-26 18:14 ` Michael Snyder
2001-03-27  0:46   ` Mark Kettenis
2001-03-27  8:45     ` Michael Snyder
2001-04-17 17:26     ` Michael Snyder
2001-04-17 23:58       ` Mark Kettenis
2001-03-26 18:35 ` Michael Snyder
2001-03-26 22:57   ` Eli Zaretskii
2001-03-27  1:13     ` Mark Kettenis
2001-03-27  1:31       ` Eli Zaretskii
2001-03-27  2:09         ` Mark Kettenis
2001-03-27  2:20           ` Eli Zaretskii
2001-03-27 10:58             ` Mark Salter
2001-03-28  1:19               ` Eli Zaretskii
2001-03-28  5:10                 ` Mark Salter
2001-03-28  5:39                   ` Eli Zaretskii
2001-03-28  8:06                     ` Mark Salter
2001-03-29 12:06                       ` Eli Zaretskii
2001-03-29 12:03                         ` Mark Salter
2001-03-27  8:55         ` Michael Snyder
2001-03-27  9:46           ` Eli Zaretskii [this message]
2001-03-27  9:55             ` Fernando Nasser
2001-03-27 11:59               ` Michael Snyder
2001-03-27 12:04                 ` Fernando Nasser
2001-03-27 11:58             ` Michael Snyder
2001-03-28  1:31               ` Eli Zaretskii
2001-03-28  2:03               ` Mark Kettenis
2001-03-27  8:52       ` Michael Snyder
2001-03-27 15:51         ` Mark Kettenis
2001-03-27 10:03       ` Andrew Cagney
2001-03-27  8:48     ` Michael Snyder
2001-03-27  9:43       ` Eli Zaretskii
2001-03-27 11:57         ` Michael Snyder
2001-03-28  1:30           ` Eli Zaretskii
2001-03-28 11:53             ` Michael Snyder
2001-03-29 12:06               ` Eli Zaretskii
     [not found] <Pine.SUN.3.91.1010329160617.4915G-100000@is>
2001-03-29 18:15 ` Mark Salter

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=200103271746.MAA08374@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    --cc=msnyder@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