Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: Pierre Muller <muller@cerbere.u-strasbg.fr>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC 3] Remove hardware break and watchpoints at program exit.
Date: Sun, 13 Jan 2002 00:31:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020113103027.6871D-100000@is> (raw)
In-Reply-To: <s3iy9j31zcm.fsf@soliton.wins.uva.nl>


On 12 Jan 2002, Mark Kettenis wrote:

> Those functions shouldn't be called when there is no debuggee.  I
> suspect that there is something wrong with the hardware
> breakpoint/watchpoint implementation at a much higher level.

The problem, IMHO, is that GDB's application level doesn't tell the
target-specific low-end that it's time to clean up the watchpoint
related data structures.  The DJGPP port uses mourn_inferior to do
that, but this might not be a good general solution, especially since
so many popular targets use the generic version of mourning.

I think we need to have code that explicitly cleans up watchpoints
when the debuggee exits.


      parent reply	other threads:[~2002-01-13  8:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11  4:01 [RFA/RFC 2] " Pierre Muller
2002-01-11  4:38 ` Eli Zaretskii
2002-01-11  4:57   ` Pierre Muller
2002-01-11  5:58     ` Eli Zaretskii
2002-01-11  5:39   ` Pierre Muller
2002-01-11  6:06     ` Eli Zaretskii
2002-01-11  8:15       ` Pierre Muller
2002-01-11  9:20       ` [RFA/RFC 3] " Pierre Muller
2002-01-12  5:20         ` Mark Kettenis
2002-01-12 13:16           ` muller
2002-01-13  0:31           ` Eli Zaretskii [this message]

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.1020113103027.6871D-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    --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