From: Joel Brobecker <brobecker@adacore.com>
To: GDB Administrator <gdbadmin@sourceware.org>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Tue May 31 01:55:32 UTC 2011
Date: Tue, 31 May 2011 05:37:00 -0000 [thread overview]
Message-ID: <20110531053707.GG2620@adacore.com> (raw)
In-Reply-To: <20110531015532.GA10047@sourceware.org>
> > gdb/valops.c:3494: code: sprintf: Do not use sprintf, instead use xsnprintf or xstrprintf
> gdb/valops.c:3494: sprintf (concatenated_name, ', namespace_name, name);
That'd be a change I made in the gdb_ari.sh script that changes
a bit the description of the 'sprintf' rule. Since this is generating
a large diff, I used the following grep sequence to verify that we
do not have any new entry that isn't a 'sprintf' entry:
% grep '^>' diff | grep -v '^>.* sprintf:'
(where diff is the contents of both ARI emails). There was no output
returned, so we can conclude that no real regression occured today.
--
Joel
prev parent reply other threads:[~2011-05-31 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 1:56 GDB Administrator
2011-05-31 5:37 ` Joel Brobecker [this message]
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=20110531053707.GG2620@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdbadmin@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