From: Doug Evans <dje@google.com>
To: Ken Werner <ken@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [unladen-swallow] Re: [RFA] Add interface for registering JITed code
Date: Fri, 21 Aug 2009 19:53:00 -0000 [thread overview]
Message-ID: <e394668d0908211214u414dbd76te7c0688a476ce6bb@mail.gmail.com> (raw)
In-Reply-To: <200908211859.04340.ken@linux.vnet.ibm.com>
On Fri, Aug 21, 2009 at 9:59 AM, Ken Werner<ken@linux.vnet.ibm.com> wrote:
>> > Hi,
>> > I noticed the gdb build fails on ppc64 if -Werror is used:
>> > gdb/jit.c: In function 'jit_event_handler':
>> > gdb/jit.c:417: warning: cast to pointer from integer of different size
>> > The attached patch uses paddress for printing the address.
>> >
>> > -ken
>>
>> Heh. Thanks.
>> Can you check it in? If not I can for you.
>
> Please go ahead since I do not have commit privileges.
> Thanks.
> -ken
>
I committed this change.
2009-08-21 Ken Werner <ken@linux.vnet.ibm.com>
Doug Evans <dje@google.com>
* jit.c (jit_event_handler): Use paddress to print target addresses.
Wrap printf string in _().
Index: jit.c
===================================================================
RCS file: /cvs/src/src/gdb/jit.c,v
retrieving revision 1.2
diff -u -p -r1.2 jit.c
--- jit.c 21 Aug 2009 18:54:44 -0000 1.2
+++ jit.c 21 Aug 2009 19:03:58 -0000
@@ -436,8 +436,8 @@ jit_event_handler (struct gdbarch *gdbar
case JIT_UNREGISTER:
objf = jit_find_objf_with_entry_addr (entry_addr);
if (objf == NULL)
- printf_unfiltered ("Unable to find JITed code entry at address: %p\n",
- (void *) entry_addr);
+ printf_unfiltered (_("Unable to find JITed code entry at
address: %s\n"),
+ paddress (gdbarch, entry_addr));
else
jit_unregister_code (objf);
next prev parent reply other threads:[~2009-08-21 19:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 1:58 Reid Kleckner
2009-07-23 12:08 ` Reid Kleckner
2009-07-23 23:21 ` Tom Tromey
2009-07-24 13:25 ` Ulrich Weigand
2009-07-24 16:52 ` Doug Evans
2009-07-25 0:40 ` [unladen-swallow] " Reid Kleckner
2009-07-24 16:55 ` Reid Kleckner
2009-07-24 20:42 ` Eli Zaretskii
2009-07-24 20:55 ` Tom Tromey
2009-07-25 15:29 ` Eli Zaretskii
2009-07-27 23:20 ` Reid Kleckner
2009-07-28 20:20 ` Eli Zaretskii
2009-07-28 22:23 ` Reid Kleckner
2009-07-29 15:20 ` Eli Zaretskii
2009-07-24 21:06 ` Tom Tromey
2009-07-25 0:23 ` Reid Kleckner
2009-07-30 16:30 ` Tom Tromey
2009-07-30 16:54 ` Tom Tromey
2009-08-05 21:05 ` [unladen-swallow] " Reid Kleckner
2009-07-30 21:10 ` Thiago Jung Bauermann
2009-07-31 18:18 ` Thiago Jung Bauermann
2009-07-31 20:31 ` [unladen-swallow] " Reid Kleckner
2009-08-01 14:43 ` Thiago Jung Bauermann
2009-08-14 19:29 ` Tom Tromey
2009-08-14 23:37 ` Reid Kleckner
2009-08-17 15:31 ` Tom Tromey
2009-08-20 18:22 ` Doug Evans
2009-08-21 15:17 ` Ken Werner
2009-08-21 16:31 ` Doug Evans
2009-08-21 18:59 ` Ken Werner
2009-08-21 19:53 ` Doug Evans [this message]
2009-07-31 20:55 ` Paul Pluzhnikov
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=e394668d0908211214u414dbd76te7c0688a476ce6bb@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=ken@linux.vnet.ibm.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