public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16324] py-finishbreakpoint.c incorrect frame_id_eq Date: Tue, 18 Oct 2022 16:33:21 +0000 [thread overview] Message-ID: <bug-16324-4717-uWagLifaeg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16324-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16324 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=04ea6b63141c43d9e96999e16917358088556fdd commit 04ea6b63141c43d9e96999e16917358088556fdd Author: Tom Tromey <tom@tromey.com> Date: Sun Jun 5 10:22:40 2022 -0600 Remove dead code from py-finishbreakpoint.c PR python/16324 points out that comparing a frame id to null_frame_id can never succeed, and proposes simply removing the dead code. That is what this patch does. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=16324 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-18 16:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-13 11:25 [Bug python/16324] New: " jan.kratochvil at redhat dot com 2014-02-24 13:02 ` [Bug python/16324] " pmuldoon at redhat dot com 2022-06-05 16:24 ` tromey at sourceware dot org 2022-10-18 16:33 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-18 16:34 ` tromey at sourceware dot org
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=bug-16324-4717-uWagLifaeg@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).