Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: pkoning@equallogic.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: proposed PATCH: make watchpoints work correctly
Date: Mon, 02 Jun 2003 04:19:00 -0000	[thread overview]
Message-ID: <9628-Mon02Jun2003072024+0300-eliz@elta.co.il> (raw)
In-Reply-To: <16086.9378.401730.788367@pkoning.dev.equallogic.com> (message from Paul Koning on Thu, 29 May 2003 11:17:54 -0400)

> Date: Thu, 29 May 2003 11:17:54 -0400
> From: Paul Koning <pkoning@equallogic.com>
> 
>  Eli> Certainly, I understand that.  I just was surprised that your
>  Eli> description of the problem was so different from my recollection
>  Eli> of how watchpoints work.
> 
> I just ran a small test case on the x86 Linux native build of gdb 5.3,
> and the problem (step works as if it were stepi, falsely reported as a
> watchpoint hit) occurs there as well -- just as expected.

Thanks, I now see the problem.

I think your solution is correct, but I'd like to minimize the number
of calls to target_stopped_data_address (they might be expensive).
Since the code already does call that function that elsewhere, could
we just reuse the result of that call, or rearrange your patch so that
a single call would do?

Otherwise, I think your change should go in.  Thanks.


  parent reply	other threads:[~2003-06-02  4:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 16:01 Paul Koning
2003-05-28 16:02 ` Paul Koning
2003-05-28 16:42 ` Daniel Jacobowitz
2003-05-28 19:54 ` Eli Zaretskii
2003-05-28 20:27   ` Paul Koning
2003-05-29  3:27     ` Eli Zaretskii
2003-05-29  4:36       ` Nathan J. Williams
2003-05-29 15:14         ` Eli Zaretskii
2003-05-29 15:17       ` Paul Koning
2003-05-29 15:37         ` Daniel Jacobowitz
2003-05-29 17:41           ` Paul Koning
2003-06-02  4:19         ` Eli Zaretskii [this message]
2003-06-04 14:51           ` Paul Koning
2003-06-29  4:15             ` Daniel Jacobowitz

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=9628-Mon02Jun2003072024+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pkoning@equallogic.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