From: "Kai Tietz" <ktietz70@googlemail.com>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, Kai.Tietz@onevision.com,
gdb-patches@sourceware.org
Subject: Re: [RFC] convert a host address to a string
Date: Sat, 10 Jan 2009 14:25:00 -0000 [thread overview]
Message-ID: <90baa01f0901100625v5668e6b6j63bfb087262248bb@mail.gmail.com> (raw)
In-Reply-To: <200901101421.n0AELbwx014532@brahms.sibelius.xs4all.nl>
2009/1/10 Mark Kettenis <mark.kettenis@xs4all.nl>:
>> Date: Sat, 10 Jan 2009 15:14:39 +0100
>> From: "Kai Tietz" <ktietz70@googlemail.com>
>>
>> 2009/1/10 Mark Kettenis <mark.kettenis@xs4all.nl>:
>> >> Date: Sat, 10 Jan 2009 14:30:29 +0100
>> >> From: "Kai Tietz" <ktietz70@googlemail.com>
>> >>
>> >> ok, so I sugget the following patch instead. It is able to generate
>> >> addresses for XP64 without the use of any vendor specific printf
>> >> formatters, and uses for targets where sizeof(long) == sizeof(void*)
>> >> the long variant.
>> >
>> > +#if defined(PRINTF_HAS_LONG_LONG) && BITSIZEOF_SIZE_T == 64 && \
>> > + SIZEOF_LONG == 4
>> > + sprintf (str, "0x%llx", (unsigned long long) (uintptr_t) addr);
>> > +#elif BITSIZEOF_SIZE_T == 64 && SIZEOF_LONG == 4
>> > + unsigned long long val = (unsigned long) (uintptr_t) addr;
>> > + if ((val & ~0xffffffffull) != 0)
>> > + sprintf (str, "0x%lx%08lx",
>> > + (unsigned long) (val >> 32), (unsigned long) val);
>> > + else
>> > + sprintf (str, "0x%lx", (unsigned long) (uintptr_t) val);
>> > +#else
>> > + sprintf (str, "0x%lx", (unsigned long) (uintptr_t) addr);
>> > +#endif
>> > return str;
>> > + BITSIZEOF_SIZE_T SIZEOF_LONG
>> >
>> > This is madness. If you go this route please do a simple
>> >
>> > const char *
>> > host_address_to_string (const void *addr)
>> > {
>> > return phex_nz ((uintptr_t)addr, sizeof(addr));
>> > }
>> >
>>
>> hmm, well, but a "0x" has to be as prefix here, isn't it?
>
> You're right. So something like:
>
> {
> char *result = get_cell ();
> xsnprintf (result, CELLSIZE, "0x%s", phex_nz((uintptr_t)addr, sizeof(addr)));
> return result;
> }
>
> perhaps?
>
Looks fine to me.
Thanks,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2009-01-10 14:25 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
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 [this message]
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=90baa01f0901100625v5668e6b6j63bfb087262248bb@mail.gmail.com \
--to=ktietz70@googlemail.com \
--cc=Kai.Tietz@onevision.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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