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 symtab/30656] [gdb/symtab] optimized out static handled inconsistently
Date: Thu, 20 Jul 2023 06:48:28 +0000 [thread overview]
Message-ID: <bug-30656-4717-tffbyiv0S9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30656-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30656
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> I wrote a dwarf assembly test-case simulating an optimized-out static
> variable:
Also reproduced with a plain C test-case:
...
$ cat whole-program.c
static int aaa;
int
main (void)
{
return 0;
}
$ gcc-12 whole-program.c -g -flto -O2
$ nm a.out | grep aaa
$
...
Corresponding DIE:
...
<1><104>: Abbrev Number: 2 (DW_TAG_variable)
<105> DW_AT_name : aaa
<109> DW_AT_decl_file : 1
<10a> DW_AT_decl_line : 1
<10b> DW_AT_decl_column : 12
<10c> DW_AT_type : <0x110>
...
Difference in behaviour:
....
$ gdb -q -batch ./a.out -ex "print aaa"
No symbol "aaa" in current context.
$ gdb -q -batch -readnow ./a.out -ex "print aaa"
$1 = <optimized out>
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-20 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 5:15 [Bug symtab/30656] New: " vries at gcc dot gnu.org
2023-07-20 6:42 ` [Bug symtab/30656] " vries at gcc dot gnu.org
2023-07-20 6:48 ` vries at gcc dot gnu.org [this message]
2023-07-20 7:35 ` vries at gcc dot gnu.org
2023-07-20 14:43 ` vries at gcc dot gnu.org
2023-07-21 6:25 ` cvs-commit at gcc dot gnu.org
2023-07-21 6:26 ` vries at gcc dot gnu.org
2023-07-21 6:51 ` vries at gcc dot gnu.org
2023-07-21 14:14 ` vries at gcc dot gnu.org
2023-07-21 14:16 ` 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-30656-4717-tffbyiv0S9@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: 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).