Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: mark.kettenis@xs4all.nl, jan.kratochvil@redhat.com,
	        gdb-patches@sourceware.org
Subject: Re: [patch] printf "%p" gdb internal error fix
Date: Tue, 04 Sep 2007 20:43:00 -0000	[thread overview]
Message-ID: <ur6letb4t.fsf@gnu.org> (raw)
In-Reply-To: <20070904141926.GA27477@caradoc.them.org> (message from Daniel 	Jacobowitz on Tue, 4 Sep 2007 10:19:26 -0400)

> Date: Tue, 4 Sep 2007 10:19:26 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
> 
> On Sun, Sep 10, 2006 at 09:31:15PM +0200, Mark Kettenis wrote:
> > > Date: Sun, 10 Sep 2006 19:20:37 +0200
> > > From: Jan Kratochvil <jan.kratochvil@redhat.com>
> > > 
> > > Hi,
> > > 
> > > (gdb) printf "%p\n", (void *) 7
> > > internal error in printf_command
> 
> > Hmm, this will not do the right thing when you try to print a 64-bit
> > pointer on a 32-bit host.
> 
> Better late than never...
> 
> Here is a patch for %p which does not rely on the size of a host
> pointer.

Thanks, but what about a companion patch for the manual?


  reply	other threads:[~2007-09-04 20:43 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
2007-09-04 14:19   ` Daniel Jacobowitz
2007-09-04 20:43     ` Eli Zaretskii [this message]
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=ur6letb4t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --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