From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [commit] fix gdbserver build failure on amd64-linux
Date: Mon, 02 Jul 2012 17:57:00 -0000 [thread overview]
Message-ID: <4FF1E0FD.1020702@earthlink.net> (raw)
In-Reply-To: <87hatqxdpz.fsf@fleche.redhat.com>
On 7/2/12 10:41 AM, Tom Tromey wrote:
> Doug> - fprintf (stderr, "at 0x%s, bp command_list is 0x%x\n",
> Doug> - paddress (where), (int) bp->command_list);
> Doug> + fprintf (stderr, "at 0x%s, bp command_list is 0x%lx\n",
> Doug> + paddress (where), (long) (uintptr_t) bp->command_list);
>
> I think it is more normal to use host_address_to_string here.
>
Or maybe dump the debug print altogether - I'm looking at it and
wondering why I ever thought this one was going to be useful. :-)
Stan
prev parent reply other threads:[~2012-07-02 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 17:12 Doug Evans
2012-07-02 17:29 ` Pedro Alves
2012-07-02 17:41 ` Tom Tromey
2012-07-02 17:57 ` Stan Shebs [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=4FF1E0FD.1020702@earthlink.net \
--to=stanshebs@earthlink.net \
--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