This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT

From: Orjan Friberg <orjan dot friberg at axis dot com>
To: gdb-patches at sources dot redhat dot com
Cc: Daniel Jacobowitz <drow at false dot org>, eliz at gnu dot org
Date: Wed, 07 Apr 2004 11:10:50 +0200
Subject: Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
Organization: Axis Communications
References: <ur81oqb1c.fsf@elta.co.il> <407282F4.2080602@axis.com> <20040406142228.GA29473@nevyn.them.org>

Daniel Jacobowitz wrote:


Presumably, the relevant part of the comment is the second half: "this
is for targets which cannot set read-only watchpoints".  On the other
hand, it does not sound like that code will work for targets which
_can_ set read-only watchpoints.  The patch was:

FWIW, the other changes from Paul's patch (returning the remote stopped data address even after single-stepping past a nonsteppable watchpoint, and (perhaps more relevant for the issue at hand) freeing the value chain for the breakpoint when inserting/deleting instead of when removing it) doesn't seem to affect this behaviour.

--
Orjan Friberg
Axis Communications

References:
- Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
  - From: Orjan Friberg
- Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]