Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@Stanford.EDU>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Option to elide single-bit bitfields when printing structures
Date: Tue, 27 Feb 2001 00:13:00 -0000	[thread overview]
Message-ID: <20010227001242.G27567@wolery.stanford.edu> (raw)
In-Reply-To: <Pine.SUN.3.91.1010225095140.10629M-100000@is>

On Sun, Feb 25, 2001 at 09:52:11AM +0200, Eli Zaretskii wrote:
> 
> On Sat, 24 Feb 2001, Zack Weinberg wrote:
> 
> > On Fri, Feb 23, 2001 at 10:05:16AM -0800, Michael Snyder wrote:
> > > 
> > > I don't think this feature is necessary.  This is just an
> > > instance of special display of data.  This is what the 
> > > gdb scripting language is for.
> > 
> > Is it, then, possible to write a gdb macro which can display an
> > arbitrary structure type in this fashion?  As far as I know, I would
> > have to write individual macros for each structure I wanted to see
> > specially.
> 
> How many such structures are there in the GCC sources?

At least 20.

zw


      reply	other threads:[~2001-02-27  0:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010222115633.B11707@wolery.stanford.edu>
     [not found] ` <200102230756.CAA06304@indy.delorie.com>
2001-02-23  7:03   ` Daniel Berlin
     [not found]     ` <6137-Fri23Feb2001183455+0200-eliz@is.elta.co.il>
2001-02-24 13:10       ` Zack Weinberg
2001-02-24 23:53         ` Eli Zaretskii
2001-02-27  0:17           ` Zack Weinberg
2001-02-27 11:04             ` Eli Zaretskii
2001-02-27 11:44               ` Daniel Berlin
2001-02-27 14:41               ` Michael Snyder
2001-02-23 10:09   ` Michael Snyder
2001-02-24 13:05     ` Zack Weinberg
2001-02-24 23:54       ` Eli Zaretskii
2001-02-27  0:13         ` Zack Weinberg [this message]

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=20010227001242.G27567@wolery.stanford.edu \
    --to=zackw@stanford.edu \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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