From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] printf "%p" gdb internal error fix
Date: Sat, 15 Sep 2007 15:18:00 -0000 [thread overview]
Message-ID: <ud4wkj6tc.fsf@gnu.org> (raw)
In-Reply-To: <20070915135229.GA15879@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 15 Sep 2007 09:52:29 -0400)
> Date: Sat, 15 Sep 2007 09:52:29 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: mark.kettenis@xs4all.nl, jan.kratochvil@redhat.com,
> gdb-patches@sourceware.org
>
> May I suggest we reference a particular C or POSIX standard if we
> are going to list exceptions?
Fine with me, but I'm not aware of the C99 document that is freely
accessible on the net. If you have a URL, by all means let's @uref
it.
> When I wrote the current
> implementation, I did it with a copy of C89 open next to me (well, I
> think - I can't find the exact manual I was using) and GCC's format
> string checker, which is a fairly definitive reference.
I looked at the glibc Info manual and a draft of C99.
next prev parent reply other threads:[~2007-09-15 15:18 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
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 [this message]
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=ud4wkj6tc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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