From: Doug Evans <dje@google.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCH] Fix PR gdb/17720 (Function names appear without namespace/class prefixes in backtrace for optimized code)
Date: Wed, 13 May 2015 20:58:00 -0000 [thread overview]
Message-ID: <CADPb22S23qPUMQyjmNMBDZmv7xz5udzVm_bWQQd+xE=_BW_eZw@mail.gmail.com> (raw)
In-Reply-To: <CADPb22RFoQk_nSbtR=HuER_Lo0qa=+1gYU7a1Bh9n2KeDgUU0A@mail.gmail.com>
On Thu, Apr 23, 2015 at 8:52 AM, Doug Evans <dje@google.com> wrote:
> On Thu, Apr 23, 2015 at 8:24 AM, Martin Galvan
> <martin.galvan@tallertechnologies.com> wrote:
>> This bug was being caused by die_needs_namespace returning 0 for a DIE whose tag was DW_TAG_inlined_subroutine. This meant that dwarf2_physname would simply return the DIE's name attribute (which in our case would be "method"). Therefore, when new_symbol_full called SYMBOL_SET_NAMES, the linkagename argument wasn't the demangled name as it should have.
>>
>> This patch adds a case which would return 1 for DW_TAG_inlined_subroutine in die_needs_namespace. It's tested both for classes and namespaces.
>>
>> I have a company-wide copyright assignment. I don't have commit access, though, so it would be great if anyone could commit this for me.
>>
>> gdb/
>> 2015-04-23 Martin Galvan <martin.galvan@tallertechnologies.com>
>>
>> * dwarf2read.c (die_needs_namespace): Return 1 for
>> DW_TAG_inlined_subroutine.
>>
>> ---
>> gdb/dwarf2read.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
>> index f6b0c01..2bf3513 100644
>> --- a/gdb/dwarf2read.c
>> +++ b/gdb/dwarf2read.c
>> @@ -8357,6 +8357,7 @@ die_needs_namespace (struct die_info *die, struct dwarf2_cu *cu)
>> case DW_TAG_enumeration_type:
>> case DW_TAG_enumerator:
>> case DW_TAG_subprogram:
>> + case DW_TAG_inlined_subroutine:
>> case DW_TAG_member:
>> case DW_TAG_imported_declaration:
>> return 1;
>
> LGTM.
> I'll check it in.
Committed.
I forgot the extra step of setting the author correctly, but it's just
one line so I'm leaving it.
next prev parent reply other threads:[~2015-05-13 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 15:25 Martin Galvan
2015-04-23 15:52 ` Doug Evans
2015-04-23 15:53 ` Martin Galvan
2015-05-11 19:48 ` Martin Galvan
2015-05-13 20:58 ` Doug Evans [this message]
2015-05-13 21:05 ` Martin Galvan
2015-05-13 21:10 ` Doug Evans
2015-05-13 21:13 ` Martin Galvan
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='CADPb22S23qPUMQyjmNMBDZmv7xz5udzVm_bWQQd+xE=_BW_eZw@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=martin.galvan@tallertechnologies.com \
/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).