Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFC] PING [Re: [PATCH] Fix macro info lookup for binaries containing DWARFv5 line table]
Date: Tue, 22 Jun 2021 10:01:56 -0700	[thread overview]
Message-ID: <ed50046c-7df6-11c3-ef6b-7d5eb5dadf8e@redhat.com> (raw)
In-Reply-To: <f9b41def-5deb-da5f-ada9-a1bee17c2fe8@redhat.com>

I think this might be something we should consider including in gdb-11.

Keith

On 6/8/21 11:48 AM, Keith Seitz via Gdb-patches wrote:
> RFC ping
> 
> Anyone at all have an opinion on this direction?
> 
> Keith
> 
> On 5/24/21 11:47 AM, Keith Seitz via Gdb-patches wrote:
>> On 5/24/21 4:36 AM, Tomar, Sourabh Singh wrote:
>>> [AMD Public Use]
>>>
>>> Hello Keith,
>>>
>>> Could you please share your plan WRT to this patch.
>>> Do you want to take it forward ? or you want me to take this forward.
>>>
>>
>> I can pursue this...
>>
>> In that vein, does anyone (maintainers?) have an input on my "counterpatch"
>> (reposted below) that removes this IS_ABSOLUTE_PREFIX stuff and copies the
>> symtab's filename?
>>
>> I haven't officially submitted this as a patch because I'm curious whether
>> my reading of this is correct/complete. Maybe the documentation/comments
>> are incorrect or no longer valid? 
>>
>> FWIW, I've tested that patch on native x86_64 Fedora 34 with no regressions.
>>
>> Keith
>>
>> Patch under discussion:
>>
>> gdb/ChangeLog
>>
>> 	* dwarf2/line-header.c (line_header::file_file_name): Copy
>> 	the symtab's filename.
>>
>> diff --git a/gdb/dwarf2/line-header.c b/gdb/dwarf2/line-header.c
>> index 7575297f966..117c5a42cc5 100644
>> --- a/gdb/dwarf2/line-header.c
>> +++ b/gdb/dwarf2/line-header.c
>> @@ -69,15 +69,10 @@ line_header::file_file_name (int file) const
>>      {
>>        const file_entry *fe = file_name_at (file);
>>  
>> -      if (!IS_ABSOLUTE_PATH (fe->name))
>> -	{
>> -	  const char *dir = fe->include_dir (this);
>> -	  if (dir != NULL)
>> -	    return gdb::unique_xmalloc_ptr<char> (concat (dir, SLASH_STRING,
>> -							  fe->name,
>> -							  (char *) NULL));
>> -	}
>> -      return make_unique_xstrdup (fe->name);
>> +      /* macro_source_file requires: "This filename is relative to the
>> +	 compilation directory, it exactly matches the symtab->filename
>> +	 content."  */
>> +      return make_unique_xstrdup (fe->symtab->filename);
>>      }
>>    else
>>      {
>>
> 


  reply	other threads:[~2021-06-22 17:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 17:16 [PATCH] Fix macro info lookup for binaries containing DWARFv5 line table Sourabh Singh Tomar via Gdb-patches
2021-05-12 17:31 ` Tomar, Sourabh Singh via Gdb-patches
2021-05-13 15:47 ` Tom Tromey
2021-05-13 18:20 ` Simon Marchi via Gdb-patches
2021-05-14 14:56 ` Keith Seitz via Gdb-patches
2021-05-14 18:21   ` Tomar, Sourabh Singh via Gdb-patches
2021-05-14 18:50     ` Simon Marchi via Gdb-patches
2021-05-14 19:20       ` Tomar, Sourabh Singh via Gdb-patches
2021-05-14 20:56         ` Simon Marchi via Gdb-patches
2021-05-24 11:36   ` Tomar, Sourabh Singh via Gdb-patches
2021-05-24 18:47     ` Keith Seitz via Gdb-patches
2021-06-08 18:48       ` Keith Seitz via Gdb-patches
2021-06-22 17:01         ` Keith Seitz via Gdb-patches [this message]
2021-06-22 20:52           ` [RFC] PING [Re: [PATCH] Fix macro info lookup for binaries containing DWARFv5 line table] Simon Marchi via Gdb-patches

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=ed50046c-7df6-11c3-ef6b-7d5eb5dadf8e@redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=keiths@redhat.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