Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	gdb-patches@sourceware.org, 	luisgpm@linux.vnet.ibm.com,
	tyrlik@us.ibm.com
Subject: Re: [PATCH 1/2] Support the new PPC476 processor -- Arch  Independent
Date: Wed, 30 Dec 2009 05:02:00 -0000	[thread overview]
Message-ID: <20091230050201.GB2788@adacore.com> (raw)
In-Reply-To: <200912292359.32931.bauerman@br.ibm.com>

> > > +	    /* We have to temporary disable this watchpoint, otherwise
> > > +	       we will count it twice (once as being inserted, and once
> > > +	       as a watchpoint that we want to insert).  */
> > > +	    e = b->enable_state;
> > > +	    b->enable_state = bp_disabled;
> > 
> > What's the story behind the need to temporarily disabling this
> > watchpoint?
> 
> This is a fix for an actual bug in the current GDB code. Jan suggested an
> improved fix. I'll post this chunk as a separate patch, and explain the
> issue there.

Please do! :-)

I just noticed that bug yesterday, and came up with yet another fix
(which is the worse of all suggestions made so far, so I won't send it,
after all [had everything ready to go, I was just waiting for our nightly
build results to come back and some of them take more than 24h]). You
and I are probably the only ones who care, because most of the
watchpoint implementations I looked at were just ignoring the count
and always returning either 1 (ok) or 0 (no more resource).

-- 
Joel


  reply	other threads:[~2009-12-30  5:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 20:49 Sérgio Durigan Júnior
2009-12-18 11:28 ` Eli Zaretskii
2009-12-29 18:55   ` Luis Machado
2009-12-29 18:59     ` Luis Machado
2009-12-30  2:00   ` Thiago Jung Bauermann
2009-12-30  5:02     ` Joel Brobecker [this message]
2009-12-30  5:11     ` Joel Brobecker
2009-12-30 17:41       ` Thiago Jung Bauermann
2009-12-30 20:44     ` 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=20091230050201.GB2788@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bauerman@br.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=luisgpm@linux.vnet.ibm.com \
    --cc=tyrlik@us.ibm.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