From: Daniel Jacobowitz <drow@false.org>
To: "Kaveh R. Ghazi" <ghazi@caipclassic.rutgers.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: add format attributes to gdb
Date: Fri, 29 Jul 2005 14:12:00 -0000 [thread overview]
Message-ID: <20050729141224.GA28517@nevyn.them.org> (raw)
In-Reply-To: <200507280310.j6S3AvjH011703@caipclassic.rutgers.edu>
On Wed, Jul 27, 2005 at 11:10:57PM -0400, Kaveh R. Ghazi wrote:
> Hi,
>
> This patch adds format attributes in various places in gdb. I found
> these mainly by compiling gdb using a snapshot of gcc-4.1.x with
> -Wmissing-format-attribute. (GCC 4.1.x has some improvements that
> find more places to add missing format attributes.)
>
> In adding these attributes, I used gdb's ATTR_FORMAT macro except
> where I worked on function pointers, in which case I used libiberty's
> ATTRIBUTE_FPTR_PRINTF. (IMHO, gdb's ATTR_FORMAT should go away in
> favor of libiberty's versions, but that's another story.)
>
> I tested this by compiling gdb-6.3.50.20050727 with a recent gcc-4.1.x
> snapshot on x86_64-unknown-linux-gnu plus I compiled gdb using
> gcc-2.95 on sparc-sun-solaris2.7 (to test that I used
> ATTRIBUTE_FPTR_PRINTF vs ATTR_FORMAT in the right places.)
>
> Note: I found zero format specifier errors! (Adding these attributes
> to gdb will help keep it that way.)
It's nice to know that we're perfect... :-)
Kaveh, my only gripe is that you've stuck these markers at the end of a
bunch of lines that were already quite long. You're past eighty columns
in a lot of places. Do you think you could fix that?
The rest of the patch looks just fine, of course.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-29 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507280310.j6S3AvjH011703@caipclassic.rutgers.edu>
2005-07-28 19:07 ` Eli Zaretskii
2005-07-28 23:05 ` Kaveh R. Ghazi
2005-07-29 14:08 ` Eli Zaretskii
2005-07-29 14:12 ` Daniel Jacobowitz [this message]
2005-07-29 17:11 ` Kaveh R. Ghazi
2005-07-31 20:57 ` Daniel Jacobowitz
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=20050729141224.GA28517@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghazi@caipclassic.rutgers.edu \
/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