From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Possible bug with i386 watchpoints on several targets.
Date: Wed, 05 Dec 2001 01:31:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011205102820.02033338@ics.u-strasbg.fr> (raw)
In-Reply-To: <Pine.SUN.3.91.1011205094734.5587C@is>
At 08:49 05/12/2001 , Eli Zaretskii a écrit:
>On Fri, 30 Nov 2001, I wrote:
>
> > The reason that hardware watchpoints are only considered to fire when
> > the watched value changes is that hardware watchpoints are treated teh
> > same as software watchpoints, and software watchpoints obviously
> > cannot fire unless the watched value changes.
> >
> > I think it is fundamentally wrong to treat hardware and software
> > watchpoints in a similar way. I think hardware watchpoints should be
> > treated like read and access watchpoints, not like software
> > watchpoints. If others (mainly Michael Snyder) agree, I will submit a
> > patch that will make that change, and will also solve this particular
> > problem raised by Pierre.
>
>Michael, did you read this part of my message? If so, do you agree with
>the principle? If you do, I'd like to write a patch that will fix this.
Eli, you didn't answer if you agree that
the call to i386_cleanup_dregs is required for all targets using
standard i386 hardware watchpoints.
I still think that the linux problem is related to that.
Your bug exists also there but its hidden by the fact
that loading shared libs at startup does set a correct value to
the value of the watched expression at the start of a program.
Which means that adding i386_cleanup_dregs call is not enough
to solve the complete problem, and that your fix is also needed.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2001-12-05 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4.2.0.58.20011121124943.00a4a288@ics.u-strasbg.fr>
[not found] ` <1190-Wed21Nov2001202555+0200-eliz@is.elta.co.il>
2001-11-30 7:18 ` Bug with watchpoints on Linux Pierre Muller
2001-11-21 16:19 ` Pierre Muller
2001-11-21 16:50 ` Eli Zaretskii
2001-11-21 17:07 ` [RFC] Possible bug with i386 watchpoints on several targets Pierre Muller
2001-11-30 8:06 ` Pierre Muller
2001-11-30 11:48 ` Eli Zaretskii
2001-11-23 6:39 ` Eli Zaretskii
2001-12-03 1:33 ` Pierre Muller
2001-12-03 3:10 ` Eli Zaretskii
2001-12-04 4:09 ` Pierre Muller
2001-12-04 23:50 ` Eli Zaretskii
2001-12-05 1:31 ` Pierre Muller [this message]
2001-12-05 3:23 ` Eli Zaretskii
2001-12-05 3:55 ` Pierre Muller
2001-11-30 7:45 ` Bug with watchpoints on Linux 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=4.2.0.58.20011205102820.02033338@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--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