From: Andrew Haley <aph@redhat.com>
To: gcc@gcc.gnu.org
Cc: gdb@sources.redhat.com
Subject: Handling aliases in debug information
Date: Wed, 24 Sep 2003 18:14:00 -0000 [thread overview]
Message-ID: <200309241445.h8OEjLJt011370@cuddles.cambridge.redhat.com> (raw)
In this program, a and b are aliases for the same variable:
int
main (int argc, char *argv[])
{
union
{
int a;
int b;
};
a = argc;
return b;
}
But debugging is hard:
cuddles:~ $ g++ -v
Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4/specs
Configured with: '/local/aph/gcc/gcc/configure' '--enable-threads=posix '--enable-languages=c,c++,java : (reconfigured)
Thread model: posix
gcc version 3.4 20030915 (experimental)
cuddles:~ $ g++ union.cc -g
cuddles:~ $ gdb ./a.out
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) b main
Breakpoint 1 at 0x8048434: file union.cc, line 10.
(gdb) r
Starting program: /cuddles/aph/home/a.out
Breakpoint 1, main (argc=1, argv=0xbfffdbc4) at union.cc:10
10 a = argc;
(gdb) n
11 return b;
(gdb) p a
No symbol "a" in current context.
(gdb) info locals
No locals.
Is this because
a. g++ is not generating good debug info for anonymous unions?
b. gdb is not interpreting g++ debug info correctly?
c. Some other reason?
Thanks,
Andrew.
next reply other threads:[~2003-09-24 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 18:14 Andrew Haley [this message]
2003-09-24 19:31 ` Elena Zannoni
2003-09-24 19:53 Michael Elizabeth Chastain
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=200309241445.h8OEjLJt011370@cuddles.cambridge.redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.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