From: Tom Tromey <tom@tromey.com>
To: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
Cc: Tom Tromey <tom@tromey.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
"simon.marchi@efficios.com" <simon.marchi@efficios.com>
Subject: Re: [PATCH] Modify align-c/align-c++ test case for AIX
Date: Fri, 17 Mar 2023 16:03:01 -0600 [thread overview]
Message-ID: <87zg8bave2.fsf@tromey.com> (raw)
In-Reply-To: <CH2PR15MB3544F4B5F9136E36A6AF2C07D6BC9@CH2PR15MB3544.namprd15.prod.outlook.com> (Aditya Kamath1's message of "Thu, 16 Mar 2023 07:01:50 +0000")
>>>>> Aditya Kamath1 <Aditya.Kamath1@ibm.com> writes:
> DW_AT_location DW_OP_addr 0xffffffff
In addition to what Ulrich said, I wonder if this behavior should have a
workaround in the gdb DWARF reader. E.g., gdb could use producer
sniffing to detect when this might happen, and then mark these symbols
as optimized out, or something along those lines.
Tom
next prev parent reply other threads:[~2023-03-17 22:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 8:57 Aditya Kamath1
2023-03-10 14:46 ` Tom Tromey
2023-03-13 13:04 ` Aditya Kamath1
2023-03-13 14:10 ` Ulrich Weigand
2023-03-15 11:52 ` Aditya Kamath1
2023-03-15 12:45 ` Tom Tromey
2023-03-16 7:01 ` Aditya Kamath1
2023-03-17 17:06 ` Ulrich Weigand
2023-03-17 22:03 ` Tom Tromey [this message]
2023-03-21 7:01 ` Aditya Kamath1
2023-03-21 7:41 ` Ulrich Weigand
2023-03-21 11:05 ` Pedro Alves
2023-03-21 14:17 ` Tom Tromey
2023-03-21 14:26 ` Ulrich Weigand
2023-03-29 11:28 ` Aditya Kamath1
2023-03-29 13:36 ` Pedro Alves
2023-03-31 12:29 ` Aditya Kamath1
2023-04-04 13:24 ` Aditya Kamath1
2023-04-05 16:33 ` Pedro Alves
2023-04-06 13:15 ` Aditya Kamath1
2023-04-06 16:18 ` Pedro Alves
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 8:56 Aditya Kamath1
2023-03-10 10:08 ` Aditya Kamath1
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=87zg8bave2.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Aditya.Kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=simon.marchi@efficios.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).