From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove dead code from py-finishbreakpoint.c
Date: Tue, 18 Oct 2022 10:29:52 -0600 [thread overview]
Message-ID: <87bkq9hz7j.fsf@tromey.com> (raw)
In-Reply-To: <20220605162904.1602810-1-tom@tromey.com> (Tom Tromey's message of "Sun, 5 Jun 2022 10:29:04 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> PR python/16324 points out that comparing a frame id to null_frame_id
Tom> can never succeed, and proposes simply removing the dead code. That
Tom> is what this patch does.
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16324
I forgot about this patch, but stumbled across the bug today. I've
rebased it and fixed it up, and now I'm checking it in.
Tom
prev parent reply other threads:[~2022-10-18 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 16:29 Tom Tromey
2022-10-18 16:29 ` 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=87bkq9hz7j.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).