Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "John Hughes" <john@Calva.COM>
To: "Eli Zaretskii" <eliz@delorie.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: RE: Patch for gdb5.0; enable hardware watchpoints on UnixWare
Date: Tue, 31 Oct 2000 06:31:00 -0000	[thread overview]
Message-ID: <NCBBLMGKIKDGJMEOMNMEGEEOHEAA.john@Calva.COM> (raw)
In-Reply-To: <200010311232.HAA21939@indy.delorie.com>

> >   could you steal the svr42mp specific bits of it for 5.1?
> >   (debug registers held in pr_family element of proc status,
> >   PCSDEBUG operation to write debug registers).
> 
> I will try, but I cannot promise this.

OK.
 
> I _will_ try to make the generic code general enough to be easily
> usable by all targets which already have watchpoint support.

What will you need?  A macro to get the debug registers for a pid
and one to put 'em back?

> >   1. Why not zap the waddr arg to go32_..._watchpoint?  It's not used.
> 
> It might be there because GDB needs that argument for some other
> (non-x86) target. 

It isn't.  GDB doesn't call go32_insert_aligned_watchpoint,
go32_insert_unaligned_watchpoint and so on.  They are only called from the
go32_insert_watchpoint, go32_remove_watchpoint in go32-nat.c (And
go32_insert_watchpoint, go32_remove_watchpoint are called from macros
in tm-xxx.h or nm-xxx,h).

> >   2. In go32_insert_aligned_watchpoint...
> 
> I think you are looking at an old version of go32-nat.c.

My comments refer to the version labeled '1.6' in the cvsweb.  Is there
a later one I could look at?  (Only if you want, please tell me to go
away if I'm wasting your time).

> While I generalize the code, I will bring it up to date with the letter
> of Intel's manuals.

So you're going to have your own defines for DR_... and not use the
system ones?  I guess that was why your code didn't match up to what
I find in sys/debugreg.h on my system.

-- 
John Hughes <john@Calva.COM>, 
        CalvaEDI SA.                            Tel: +33-1-4313-3131
        66 rue du Moulin de la Pointe,          Fax: +33-1-4313-3139
        75013 PARIS.


  reply	other threads:[~2000-10-31  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NCBBLMGKIKDGJMEOMNMEEEDMHEAA.john@Calva.COM>
     [not found] ` <NCBBLMGKIKDGJMEOMNMEMEELHEAA.john@Calva.COM>
2000-10-31  4:32   ` Eli Zaretskii
2000-10-31  6:31     ` John Hughes [this message]
2000-10-31  9:10       ` Eli Zaretskii

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=NCBBLMGKIKDGJMEOMNMEGEEOHEAA.john@Calva.COM \
    --to=john@calva.com \
    --cc=eliz@delorie.com \
    --cc=gdb-patches@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