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 gdb/26683] FAIL: gdb.base/info-types-c++.exp: info types Date: Wed, 30 Sep 2020 15:48:16 +0000 [thread overview] Message-ID: <bug-26683-4717-XW0aejpyma@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26683-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26683 --- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> --- Tentative patch: ... diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c index 70d2091148..57e2ce77bf 100644 --- a/gdb/dwarf2/read.c +++ b/gdb/dwarf2/read.c @@ -22633,6 +22633,7 @@ dwarf2_name (struct die_info *die, struct dwarf2_cu *cu) if (!attr || attr_name == NULL) { attr = dw2_linkage_name_attr (die, cu); + attr_name = attr == nullptr ? nullptr : attr->as_string (); if (attr == NULL || attr_name == NULL) return NULL; @@ -22647,6 +22648,7 @@ dwarf2_name (struct die_info *die, struct dwarf2_cu *cu) DW_STRING (attr) = objfile->intern (demangled.get ()); DW_STRING_IS_CANONICAL (attr) = 1; + attr_name = attr->as_string (); } /* Strip any leading namespaces/classes, keep only the ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-30 15:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-30 14:10 [Bug gdb/26683] New: " vries at gcc dot gnu.org 2020-09-30 14:51 ` [Bug gdb/26683] " vries at gcc dot gnu.org 2020-09-30 15:05 ` vries at gcc dot gnu.org 2020-09-30 15:10 ` vries at gcc dot gnu.org 2020-09-30 15:48 ` vries at gcc dot gnu.org [this message] 2020-09-30 17:05 ` tromey at sourceware dot org 2020-09-30 19:47 ` [Bug symtab/26683] " vries at gcc dot gnu.org 2020-09-30 19:49 ` cvs-commit at gcc dot gnu.org 2020-09-30 19:49 ` 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-26683-4717-XW0aejpyma@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).