From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Handling of structure dereferencing
Date: Thu, 06 Dec 2001 09:07:00 -0000 [thread overview]
Message-ID: <20011206120739.A1490@nevyn.them.org> (raw)
Right now, and historically, gdb has accepted things like:
struct foo {char a} *b, **c, ***d;
(gdb) print b.a
(gdb) print d->a
This is tied to a collection of very messy values handling, where we will
dereference pointers "as far as possible" in a lot of cases (like when
looking for members). It makes printing structs somewhat "easier", but in
my opinion, also rather more confusing.
So, straw poll: how would people feel about:
- not letting this happen; only explicit dereferencing
[random thought]
- and maybe, a print flag or something to allow us to print both the
value of a pointer and the dereferenced type by default. I spend a lot
of time doing "print longthing" up arrow "print longthing[0]" up arrow
"print longthing[0].otherfield" to walk down things like "struct type";
it would be nice if there were a way to do the first two steps at the same
time, since they are so very often associated.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2001-12-06 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 9:07 Daniel Jacobowitz [this message]
2001-12-06 11:48 ` Eli Zaretskii
2001-12-06 12:43 ` Daniel Jacobowitz
2002-01-02 20:25 ` Andrew Cagney
2002-02-05 9:31 ` Daniel Berlin
2002-02-05 10:17 ` Daniel Jacobowitz
2001-12-06 15:41 ` Tom Tromey
2001-12-06 23:36 ` Eli Zaretskii
2001-12-06 9:46 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=20011206120739.A1490@nevyn.them.org \
--to=drow@mvista.com \
--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