From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: Complex location
Date: Thu, 18 Jan 2007 16:20:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20070118170619.01863050@NT_SERVER> (raw)
Hi
Gdb (6.5) often just says:
(gdb) info scope Inos.cpp:556
Scope for Inos.cpp:556:
Symbol this is a variable with complex or multiple locations (DWARF2), length 4.
Symbol var1 is a variable with complex or multiple locations (DWARF2), length 4.
Symbol var2 is a variable with complex or multiple locations (DWARF2), length 4.
However how can this be complex?
void CClass::DoIt()
{
CObject* var1=(CObject*)0x12345678;
CObject* var2=(CObject*)0x23232323;
...
Shouldn't gdb be able to say something like "variable on stack at offset 0x10" or
something along this?
The only thing I could find is:
http://sourceware.org/ml/gdb/2003-07/msg00243.html
"In general, we need a location expression pretty-printer - this is
quite complicated, so no one's done it yet."
Seems like that is still the case, is that correct?
Thanks
Bye Fabi
next reply other threads:[~2007-01-18 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 16:20 Fabian Cenedese [this message]
2007-01-18 16:32 ` Daniel Jacobowitz
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=5.2.0.9.1.20070118170619.01863050@NT_SERVER \
--to=cenedese@indel.ch \
--cc=gdb@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