From: "Tomar, Sourabh Singh" <SourabhSingh.Tomar@amd.com>
To: Keith Seitz <keiths@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
"Achra, Nitika" <Nitika.Achra@amd.com>,
"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>,
"Kumar N, Bhuvanendra" <Bhuvanendra.KumarN@amd.com>
Subject: RE: Macro info NOT accessible with GDB-trunk
Date: Mon, 17 May 2021 17:04:36 +0000 [thread overview]
Message-ID: <DM4PR12MB52954D49AD3DFB942D8561EB9D2D9@DM4PR12MB5295.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5e4ae21e-6236-067e-18ce-88e165bcfb82@redhat.com>
[AMD Public Use]
Thanks For the quick response keith!
Do you have any pointers to the base commit/change that might've caused this ?
IIRC, it was working fine couple og weeks back (That was the foundation of my initial patch that
things were working fine with GCC and not with CLANG). Now as it seems GCC generated binaries are also
not showing macro info at all ☹
Thanks!
Sourabh.
-----Original Message-----
From: Keith Seitz <keiths@redhat.com>
Sent: Monday, May 17, 2021 10:21 PM
To: Tomar, Sourabh Singh <SourabhSingh.Tomar@amd.com>; gdb@sourceware.org
Cc: George, Jini Susan <JiniSusan.George@amd.com>; Achra, Nitika <Nitika.Achra@amd.com>; Sharma, Alok Kumar <AlokKumar.Sharma@amd.com>; Kumar N, Bhuvanendra <Bhuvanendra.KumarN@amd.com>
Subject: Re: Macro info NOT accessible with GDB-trunk
[CAUTION: External Email]
On 5/17/21 9:35 AM, Tomar, Sourabh Singh via Gdb wrote:
> Can somebody please validate this ?
>
Yes, I can verify this, and I've posted a tentative patch to fix this in your gdb-patches thread titled "Fix macro info lookup for binaries containing DWARFv5 line table."
It's here:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceware.org%2Fpipermail%2Fgdb-patches%2F2021-May%2F178871.html&data=04%7C01%7Csourabhsingh.tomar%40amd.com%7C505927ec7b8b45e9579e08d91953f963%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637568670724930270%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9ZB%2BPsvD9GZrlMZZpLE5Ild8mJVpjJzWxGq%2FcrSWOkY%3D&reserved=0
This is also reported as gdb/27306.
Keith
next prev parent reply other threads:[~2021-05-17 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 16:35 Tomar, Sourabh Singh
2021-05-17 16:51 ` Keith Seitz
2021-05-17 17:04 ` Tomar, Sourabh Singh [this message]
2021-05-17 17:17 ` Tomar, Sourabh Singh
2021-05-17 17:22 ` Keith Seitz
2021-09-16 4:18 ` Achra, Nitika
2021-10-04 3:46 ` Achra, Nitika
2021-10-06 16:11 ` Keith Seitz
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=DM4PR12MB52954D49AD3DFB942D8561EB9D2D9@DM4PR12MB5295.namprd12.prod.outlook.com \
--to=sourabhsingh.tomar@amd.com \
--cc=AlokKumar.Sharma@amd.com \
--cc=Bhuvanendra.KumarN@amd.com \
--cc=JiniSusan.George@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).