From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Rewrite bplocpy_repr
Date: Wed, 21 Oct 2026 11:32:34 -0600 [thread overview]
Message-ID: <87v76vx8lp.fsf@tromey.com> (raw)
In-Reply-To: <20260911154726.667576-1-tromey@adacore.com> (Tom Tromey's message of "Fri, 11 Sep 2026 09:47:26 -0600")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> A user pointed out that printing the repr() of a watchpoint location
Tom> will cause gdb to crash. See the new test in py-breakpoint.exp.
Tom> Rather than try to fix this directly, it seemed better to me to have
Tom> this function call bp_location::to_string. This call omits a bit of
Tom> useful information so the enabled state is still handled in
Tom> bplocpy_repr.
I'm checking this in.
Tom
prev parent reply other threads:[~2026-10-21 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:47 Tom Tromey
2026-10-21 17:32 ` Tom Tromey [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=87v76vx8lp.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.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