Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix watchpoints when stepping over a breakpoint
Date: Fri, 05 Apr 2002 09:55:00 -0000	[thread overview]
Message-ID: <3CADE514.7020908@cygnus.com> (raw)
In-Reply-To: <20020405120851.A17113@nevyn.them.org>

> Also bear in mind that if you have this sequence:
> - write to x
> - other instruction    <--- breakpoint here
> You will stop based on the watchpoint, because the watchpoint happens
> first.  You'll get a trap just before you would have hit the
> breakpoint. GDB handles this OK, and does report the watchpoint.  It's
> only if we expected a trap (single stepping for instance) that this
> does not work.  The current failure is "single step over something
> which triggers the watchpoint, landing on something with a breakpoint". 
> Without my patch, we detect that we are at an address with a
> breakpoint, and don't even try to check our watchpoints.

I suspect this is a design problem.  Blame DECR_PC?  The ``stop'' 
address gets confused with the PC value and the decr's probably screw it.

Andrew


  reply	other threads:[~2002-04-05 17:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 15:43 Daniel Jacobowitz
2002-04-04 23:38 ` Eli Zaretskii
2002-04-05  7:54   ` Daniel Jacobowitz
2002-04-05  8:45     ` Eli Zaretskii
2002-04-05  9:08       ` Daniel Jacobowitz
2002-04-05  9:55         ` Andrew Cagney [this message]
2002-04-05 23:48         ` Eli Zaretskii
2002-04-06  7:36           ` Daniel Jacobowitz
2002-04-06  9:21             ` Eli Zaretskii
2002-04-06  9:49               ` Daniel Jacobowitz
2002-04-07  9:16                 ` Andrew Cagney
2002-04-07 10:03                   ` Eli Zaretskii
2002-04-14 14:49                     ` Andrew Cagney
2002-04-14 22:07                       ` Eli Zaretskii
2002-04-18 18:34                         ` Andrew Cagney
2002-04-02 22:18 Michael Elizabeth Chastain

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=3CADE514.7020908@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=eliz@is.elta.co.il \
    --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