From: Daniel Jacobowitz <drow@false.org>
To: "Stefan Burström" <f94sbu@efd.lth.se>
Cc: gdb@sources.redhat.com
Subject: Re: info types question
Date: Tue, 22 Nov 2005 23:45:00 -0000 [thread overview]
Message-ID: <20051122232047.GA32223@nevyn.them.org> (raw)
In-Reply-To: <3477723caab.6257669c@mail.m.bonet.se>
On Wed, Nov 23, 2005 at 12:01:54AM +0100, Stefan Burström wrote:
> I was wondering what kind of output I can expect from 'info types'?
> I am getting some sensible output such as
>
> typedef int mytype;
>
> but I am also getting output such as
>
> typedef double;
>
> and
>
> typedef long long unsigned int;
>
> The former I guess doesn't really matter, but the later really defines int
> to be an unsigned 64 bit type. Which cannot be what is desired?
> Of course I can ignore all types defined int libgcc2.c but I'd like to find
> out the 'logic' behind this.
These probably indicate "typedefs" without a name, probably definitions
of base types.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-22 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 8:39 First release candidate for GDB 6.4 available Joel Brobecker
2005-11-22 14:09 ` Daniel Jacobowitz
2005-11-25 5:28 ` Randolph Chung
2005-11-22 23:16 ` Ulrich Weigand
2005-11-22 23:20 ` Mark Kettenis
2005-11-22 23:20 ` info types question Stefan Burström
2005-11-22 23:45 ` Daniel Jacobowitz [this message]
2005-11-22 23:50 ` Stefan Burström
2005-11-25 3:09 ` Daniel Jacobowitz
2005-11-23 5:17 ` First release candidate for GDB 6.4 available Wu Zhou
2005-11-25 2:47 ` Mark Kettenis
2005-11-25 2:51 ` Wu Zhou
2005-11-25 3:15 ` Daniel Jacobowitz
2005-11-25 4:21 ` Wu Zhou
2005-11-25 15:57 ` Kunal Parmar
2005-11-28 22:44 ` Mark Kettenis
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=20051122232047.GA32223@nevyn.them.org \
--to=drow@false.org \
--cc=f94sbu@efd.lth.se \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).