From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] [gdb/build] Fix static cast of virtual base
Date: Fri, 23 Feb 2024 06:56:35 -0700 [thread overview]
Message-ID: <87cysnz3l8.fsf@tromey.com> (raw)
In-Reply-To: <20240222161804.1134-1-tdevries@suse.de> (Tom de Vries's message of "Thu, 22 Feb 2024 17:18:04 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Fix this by using dynamic_cast instead of gdb::checked_static_cast in
Tom> TUI_CMD_WIN and TUI_STATUS_WIN.
Tom> Tested on x86_64-linux, with development set to false.
Tom> Reported-By: Robert Xiao <spam_hole@shaw.ca>
Tom> Reported-By: Simon Marchi <simark@simark.ca>
Tom> PR build/31399
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31399
Ok. Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2024-02-23 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 16:18 Tom de Vries
2024-02-23 13:56 ` Tom Tromey [this message]
2024-03-06 17:39 ` Andrew Burgess
2024-03-06 18:27 ` Simon Marchi
2024-03-08 16:18 ` Tom Tromey
2024-03-11 10:25 ` Andrew Burgess
2024-03-11 16:22 ` Simon Marchi
2024-03-19 14:58 ` Andrew Burgess
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=87cysnz3l8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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).