From: Phil Richards <news@derived-software.ltd.uk>
To: git@vger.kernel.org
Subject: Re: Enable the packed refs file format
Date: Wed, 20 Sep 2006 21:19:30 +0100 (BST) [thread overview]
Message-ID: <20060920201930.9E48F487D@derisoft.derived-software.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0609191407340.4388@g5.osdl.org>
On 2006-09-19, Linus Torvalds <torvalds@osdl.org> wrote:
> Too bad that we can't get gcc to warn on these things. We do mark it as
> "format(printf)", but I don't know of any way to tell gcc that it _has_ to
> have that initial constant string.
Not sure if it just a gcc 4.x-ism, but -Wformat-nonliteral or -Wformat-security
might be what you are looking for.
`-Wformat-nonliteral'
If `-Wformat' is specified, also warn if the format string is not a
string literal and so cannot be checked, unless the format function
takes its format arguments as a `va_list'.
`-Wformat-security'
If `-Wformat' is specified, also warn about uses of format
functions that represent possible security problems. At present,
this warns about calls to `printf' and `scanf' functions where the
format string is not a string literal and there are no format
arguments, as in `printf (foo);'. This may be a security hole if
the format string came from untrusted input and contains `%n'.
(This is currently a subset of what `-Wformat-nonliteral' warns
about, but in future warnings may be added to `-Wformat-security'
that are not included in `-Wformat-nonliteral'.)
phil
--
change name before "@" to "phil" for email
next prev parent reply other threads:[~2006-09-20 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 17:14 Enable the packed refs file format Linus Torvalds
2006-09-19 20:55 ` Petr Baudis
2006-09-19 21:09 ` Linus Torvalds
2006-09-20 20:19 ` Phil Richards [this message]
2006-09-22 23:08 ` [PATCH] Fix buggy ref recording Petr Baudis
2006-09-23 0:44 ` Junio C Hamano
2006-09-23 1:16 ` Petr Baudis
2006-09-23 4:34 ` [PATCH] pack-refs: fix git_path() usage Junio C Hamano
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=20060920201930.9E48F487D@derisoft.derived-software.demon.co.uk \
--to=news@derived-software.ltd.uk \
--cc=git@vger.kernel.org \
--cc=spams@derived-software.demon.co.uk \
/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 NNTP newsgroup(s).