Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org,
	 Guinevere Larsen <guinevere@redhat.com>,
	Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Subject: Re: [PATCH v2] Prevent downgrading of hardware watchpoints if possible
Date: Fri, 21 Aug 2026 11:55:56 -0600	[thread overview]
Message-ID: <875x13qrwz.fsf@tromey.com> (raw)
In-Reply-To: <20260727150150.1014621-1-ssbssa@yahoo.de> (Hannes Domani's message of "Mon, 27 Jul 2026 16:57:01 +0200")

>>>>> "Hannes" == Hannes Domani <ssbssa@yahoo.de> writes:

Hannes> The lazy flag of a value can tell us if the value contents are available.
Hannes> But this could be either because it was simply never actually accessed,
Hannes> or it tried to be accessed, and failed.
Hannes> The latter are interesting for watchpoints, the former are not.

Hannes> Currently it only uses lazy values if they are at the head of the value
Hannes> chain, but this is fragile logic, and degrades some watchpoints to
Hannes> software watchpoints where it's actually not necessary.

Hannes> So this adds a new value flag 'm_fetch_lazy_failed' which tells if the
Hannes> watchpoint expression actually tried to access the value and failed.
Hannes> And this is used instead of the value chain location to tell if a lazy
Hannes> value should be used as a watchpoint location.

Thanks for doing this.  I think this is ok.
Approved-By: Tom Tromey <tom@tromey.com>

Tom

  parent reply	other threads:[~2026-08-21 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260727150150.1014621-1-ssbssa.ref@yahoo.de>
2026-07-27 14:57 ` Hannes Domani
2026-08-10 17:20   ` Hannes Domani
2026-08-21 17:55   ` Tom Tromey [this message]
2026-08-23 16:52     ` Hannes Domani

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=875x13qrwz.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=ssbssa@yahoo.de \
    --cc=thiago.bauermann@linaro.org \
    /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