Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] printf "%p" gdb internal error fix
Date: Sun, 10 Sep 2006 22:00:00 -0000	[thread overview]
Message-ID: <20060910220026.GA6115@nevyn.them.org> (raw)
In-Reply-To: <200609101931.k8AJVF4m026090@elgar.sibelius.xs4all.nl>

On Sun, Sep 10, 2006 at 09:31:15PM +0200, Mark Kettenis wrote:
> Hmm, this will not do the right thing when you try to print a 64-bit
> pointer on a 32-bit host.

True, though, neither will the rest of the printf code:

          case long_arg:
            {
              long val = value_as_long (val_args[i]);
              printf_filtered (current_substring, val);
              break;
            }

None of it is written to use target types at present, only host types.
It'd need even more surgery if you wanted it to, since
current_substring gets passed to the host's printf.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-09-10 22:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-10 17:20 Jan Kratochvil
2006-09-10 19:31 ` Mark Kettenis
2006-09-10 22:00   ` Daniel Jacobowitz [this message]
2007-09-04 14:19   ` Daniel Jacobowitz
2007-09-04 20:43     ` Eli Zaretskii
2007-09-04 20:53       ` Daniel Jacobowitz
2007-09-15  9:00         ` Eli Zaretskii
2007-09-15 13:52           ` Daniel Jacobowitz
2007-09-15 14:55             ` Andreas Schwab
2007-09-15 15:16               ` Eli Zaretskii
2007-09-15 15:18             ` Eli Zaretskii
2007-09-15 16:12               ` Daniel Jacobowitz
2007-09-15 18:12                 ` Eli Zaretskii
2007-09-15 18:40                   ` Daniel Jacobowitz
2007-09-15 21:59                     ` Eli Zaretskii
2007-09-15 22:17                       ` Daniel Jacobowitz
2007-09-15 16:21               ` Joseph S. Myers

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=20060910220026.GA6115@nevyn.them.org \
    --to=drow@false.org \
    --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