Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] dwarf2read.c: complain() -> complaint()
Date: Tue, 10 Dec 2002 09:03:00 -0000	[thread overview]
Message-ID: <1021210163223.ZM23042@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: [RFA] dwarf2read.c: complain() -> complaint()" (Dec 10, 11:13am)

On Dec 10, 11:13am, Andrew Cagney wrote:

> Definitly fine with the theory.  Two reservations (really just one).
> 
> - how is the result with -Wformat?  The reason behind switching from 
> complain() to complaint was to get the parameters checked and hence find 
> some nasty address printing bugs.

No warnings.  (I was looking for this too when I eyeballed the resulting
patch.)

> - I suspect it will need a visual audit to check for any cases of:
> 	"%08lx", (long) core_addr_variable

Yes, I agree.  At the moment my script is only smart enough to handle
the cases that occur in dwarf2read.c.  An excerpt:

		# yes, this is naive, but it's all we need for dwarf2read.c...
		$formals .= 'const char *' if $1 eq 's';
		$formals .= 'long'         if $1 eq 'l';
		$formals .= 'int'          if $1 eq 'd';
		$formals .= 'int'          if $1 eq 'x';

I'll augment the script as I go...  In some cases, hand edits may be
necessary.

Kevin


  reply	other threads:[~2002-12-10 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 15:42 Kevin Buettner
2002-12-10  8:32 ` Andrew Cagney
2002-12-10  9:03   ` Kevin Buettner [this message]
2002-12-11 10:47   ` Jim Blandy
2002-12-11 12:23     ` Andrew Cagney
2002-12-11 14:15       ` Jim Blandy
2002-12-11 14:34         ` Andrew Cagney
2002-12-11 13:02 ` Kevin Buettner

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=1021210163223.ZM23042@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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