Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Kai.Tietz@onevision.com
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFC] convert a host address to a string
Date: Thu, 08 Jan 2009 12:49:00 -0000	[thread overview]
Message-ID: <200901081249.n08Cn6WB031507@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <OFC93D38E8.E9DC11CD-ONC1257538.003C224C-C1257538.003C9AEB@onevision.de> 	(message from Kai Tietz on Thu, 8 Jan 2009 12:01:56 +0100)

> From: Kai Tietz <Kai.Tietz@onevision.com>
> Date: Thu, 8 Jan 2009 12:01:56 +0100
> 
> Joel Brobecker <brobecker@adacore.com> wrote on 08.01.2009 11:48:00:
> 
> > > Why not simply use stdint.h (gstdint.h) for this?
> > 
> > Could you give more details? I'm not sure what you mean exactly.
> > 
> > Thanks,
> > -- 
> > Joel
> > 
> 
> By it you can use standard ISO type intptr_t. And I missed to add 
> inttypes.h.
> By this you could simply use PRIXPTR for printing hex pointer failues.
> 
> E.g.
>  fprint (fp, "0x%" PRIXPTR, (intptr_t) address);

Well, the PRIxxx macros are ISO C99 inventions, so we can't assume
they're generally available.  Guess that could be mitigated by
importing inttypes module from gnulib.


  parent reply	other threads:[~2009-01-08 12:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 12:19 Joel Brobecker
2009-01-07 16:17 ` Mark Kettenis
2009-01-08 10:19   ` Joel Brobecker
2009-01-08 10:25     ` Kai Tietz
2009-01-08 10:48       ` Joel Brobecker
2009-01-08 11:02         ` Kai Tietz
2009-01-08 11:25           ` Joel Brobecker
2009-01-08 11:31             ` Kai Tietz
2009-01-08 12:49           ` Mark Kettenis [this message]
2009-01-08 12:54             ` Joel Brobecker
2009-01-08 13:04               ` Kai Tietz
2009-01-08 13:12               ` Mark Kettenis
2009-01-08 13:26     ` Mark Kettenis
2009-01-08 13:35       ` Kai Tietz
2009-01-08 13:42         ` Joel Brobecker
2009-01-08 14:04           ` Kai Tietz
2009-01-08 16:18         ` Mark Kettenis
2009-01-08 16:23           ` Kai Tietz
2009-01-09  9:57             ` Joel Brobecker
2009-01-09 10:05               ` Kai Tietz
2009-01-09 13:12       ` Joel Brobecker
2009-01-09 14:28         ` Kai Tietz
2009-01-10  7:12           ` Joel Brobecker
2009-01-10 13:31             ` Kai Tietz
2009-01-10 13:34               ` Kai Tietz
2009-01-10 13:58               ` Mark Kettenis
2009-01-10 14:04               ` Mark Kettenis
2009-01-10 14:15                 ` Kai Tietz
2009-01-10 14:22                   ` Mark Kettenis
2009-01-10 14:25                     ` Kai Tietz
2009-01-11 13:31                     ` Joel Brobecker
2009-01-11 13:53                       ` Mark Kettenis
2009-01-13 12:09                     ` Joel Brobecker

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=200901081249.n08Cn6WB031507@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=Kai.Tietz@onevision.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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