Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: Handling of structure dereferencing
Date: Thu, 06 Dec 2001 11:48:00 -0000	[thread overview]
Message-ID: <7263-Thu06Dec2001214750+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20011206120739.A1490@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 6 Dec 2001 12:07:39 -0500)

> Date: Thu, 6 Dec 2001 12:07:39 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> 
> Right now, and historically, gdb has accepted things like:
>   struct foo {char a} *b, **c, ***d;
> 
> (gdb) print b.a
> (gdb) print d->a

You mean, instead of b->a and (**d)->a, yes?

> So, straw poll: how would people feel about:
>  - not letting this happen; only explicit dereferencing

I don't mind in this specific case, but I wonder whether there isn't
some iceberg of which this is only a tip.  We do want GDB to continue
to print a string when you say "p str", and str is a pointer to a
string, right?  It's quite possible that the same machinery which
supports printing arrays also causes the above.


  reply	other threads:[~2001-12-06 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06  9:07 Daniel Jacobowitz
2001-12-06 11:48 ` Eli Zaretskii [this message]
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=7263-Thu06Dec2001214750+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=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