Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: integer types in gdb code
Date: Mon, 27 Jan 2003 21:17:00 -0000	[thread overview]
Message-ID: <3E35A1DC.7040506@redhat.com> (raw)
In-Reply-To: <10cd01c2c646$4c9cccb0$0202040a@catdog>

>
>> CORE_ADDR  ~= void *
>> LONGEST ~= long
>> ULONGEST ~= unsigned long
> 
> 
> No 16 and 8 bit constructs?  Also, what if you want to guarantee the number
> of bits?  From defs.h it looks to me like LONGEST could be 32 or 64 bits, so
> if you're reading structures over the wire, you could have problems.

The above are GDB's host types.

When representing target types (or stuff related to a protocol) GDB can 
either use a function like extract_unsigned_integer() or construct a 
type exactly describing the data using that (but be wary of byte order 
problems).

Trying to do something like:

struct { uint32_t i; ... }

can end up being non-portable (due to struct packing issues and the like).

Andrew



      reply	other threads:[~2003-01-27 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-27 19:55 Kris Warkentin
2003-01-27 20:40 ` Andrew Cagney
2003-01-27 20:54   ` Kris Warkentin
2003-01-27 21:17     ` Andrew Cagney [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=3E35A1DC.7040506@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=kewarken@qnx.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