public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/25955] FAIL: gdb.mi/mi-catch-cpp-exceptions.exp: all with invalid regexp: run until breakpoint in main (unknown output after running) Date: Sat, 09 May 2020 12:08:05 +0000 [thread overview] Message-ID: <bug-25955-4717-ejBOAKgzsU@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25955-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25955 --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- Tentative patch: ... diff --git a/gdb/break-catch-throw.c b/gdb/break-catch-throw.c index 59293c4e57..7f4a9f955d 100644 --- a/gdb/break-catch-throw.c +++ b/gdb/break-catch-throw.c @@ -166,7 +166,7 @@ check_status_exception_catchpoint (struct bpstats *bs) type_name = cplus_typename_from_type_info (typeinfo_arg); canon = cp_canonicalize_string (type_name.c_str ()); - name = (canon == nullptr + name = (canon != nullptr ? canon.get () : type_name.c_str ()); } ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-09 12:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-09 10:20 [Bug c++/25955] New: " vries at gcc dot gnu.org 2020-05-09 10:20 ` [Bug c++/25955] " vries at gcc dot gnu.org 2020-05-09 10:24 ` vries at gcc dot gnu.org 2020-05-09 11:31 ` vries at gcc dot gnu.org 2020-05-09 12:02 ` vries at gcc dot gnu.org 2020-05-09 12:08 ` vries at gcc dot gnu.org [this message] 2020-05-09 12:24 ` [Bug gdb/25955] " vries at gcc dot gnu.org 2020-05-09 18:17 ` cvs-commit at gcc dot gnu.org 2020-05-09 18:19 ` vries at gcc dot gnu.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-25955-4717-ejBOAKgzsU@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).