From: Eli Zaretskii <eliz@is.elta.co.il>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Possible bug with i386 watchpoints on several targets.
Date: Wed, 05 Dec 2001 03:23:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1011205131342.7196A-100000@is> (raw)
In-Reply-To: <4.2.0.58.20011205102820.02033338@ics.u-strasbg.fr>
On Wed, 5 Dec 2001, Pierre Muller wrote:
> 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 don't know; theoretically, GDB should remove all the watchpoints from
the debuggee on the way to exit. If all watchpoints are removed, the
dr_* variables are cleaned up automatically.
But an explicit call to i386_cleanup_dregs when the debuggee dies cannot
possibly do any harm, so there should be no reason not to do that, if it
is sometimes needed.
next prev parent reply other threads:[~2001-12-05 11:23 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
2001-12-05 3:23 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1011205131342.7196A-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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