From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Keith Seitz'" <keiths@redhat.com>
Cc: "'Patrick Monnerat'" <Patrick.Monnerat@datasphere.ch>,
<insight@sourceware.org>, <roland@onevision.com>
Subject: RE: [PATCH] print format does not match argument type
Date: Fri, 13 Apr 2012 15:25:00 -0000 [thread overview]
Message-ID: <000001cd1989$9387b1d0$ba971570$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <4F884387.90807@redhat.com>
> -----Message d'origine-----
> De : insight-owner@sourceware.org [mailto:insight-owner@sourceware.org] De
> la part de Keith Seitz
> Envoyé : vendredi 13 avril 2012 17:17
> À : Pierre Muller
> Cc : 'Patrick Monnerat'; insight@sourceware.org; roland@onevision.com
> Objet : Re: [PATCH] print format does not match argument type
>
> On 04/13/2012 07:52 AM, Pierre Muller wrote:
> > The gdb/utils.c function called host_address_to_string
> > was created to allow printing of host pointer
> > without need to bother with %llX or typecasts...
> >
> > It does add a '0x' at the start of the
> > generated pchar, but I don't think that this is a big problem.
> >
> > This second field (ar[1]) is probably added to avoid confusion between
> > type with same name...
> >
> > Should we use this patch?
>
> Yes, thank you for pointing that out. I just *knew* there had to be a
> way to do this "safely." [As safe as it can be to pass host pointers
> into the interpreter at least.]
Patch committed in
http://sourceware.org/ml/gdb-cvs/2012-04/msg00086.html
Thanks
Pierre
next prev parent reply other threads:[~2012-04-13 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 14:30 Roland Schwingel
2012-04-10 15:10 ` Patrick Monnerat
2012-04-10 16:08 ` Patrick Monnerat
2012-04-10 16:28 ` Keith Seitz
2012-04-13 14:52 ` Pierre Muller
2012-04-13 15:18 ` Keith Seitz
2012-04-13 15:25 ` Pierre Muller [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-11 11:38 Roland Schwingel
2012-04-11 17:24 ` Patrick Monnerat
2012-04-10 16:59 Roland Schwingel
2012-04-05 16:34 Patrick Monnerat
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='000001cd1989$9387b1d0$ba971570$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=Patrick.Monnerat@datasphere.ch \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
--cc=roland@onevision.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).