From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <devans@sourceware.org>
Cc: <gdb-patches@sourceware.org>
Subject: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
Date: Tue, 06 Nov 2012 11:08:00 -0000 [thread overview]
Message-ID: <007101cdbc0f$07a68fa0$16f3aee0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20121106015848.GA5296@sourceware.org>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de GDB Administrator
> Envoyé : mardi 6 novembre 2012 02:59
> À : gdb-patches@sourceware.org
> Objet : New ARI warning Tue Nov 6 01:58:48 UTC 2012
>
> 281a282,283
> > gdb/dwarf2read.c:8612: regression: xasprintf: Do not use xasprintf(),
> instead use xstrprintf
> gdb/dwarf2read.c:8612: xasprintf (&virtual_dwo_name, ',
> > gdb/dwarf2read.c:8984: regression: xasprintf: Do not use xasprintf(),
> instead use xstrprintf
> gdb/dwarf2read.c:8984: xasprintf (&dwp_name, ', dwarf2_per_objfile-
> >objfile->name);
Doug,
could you check the patch below
which removes the new ARI warnings about use of
xasprintf function in the commit
http://sourceware.org/ml/gdb-cvs/2012-11/msg00027.html
Pierre Muller
ChangeLog entry:
2012-11-06 Pierre Muller <muller@sourceware.org>
ARI xasprintf rule fixes.
* dwarf2read.c (create_dwo_in_dwp): Use xstrprintf function
instead of xasprintf.
(open_and_init_dwp_file): Ditto.
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.710
diff -u -p -r1.710 dwarf2read.c
--- dwarf2read.c 5 Nov 2012 15:50:21 -0000 1.710
+++ dwarf2read.c 6 Nov 2012 11:00:17 -0000
@@ -8609,13 +8609,14 @@ create_dwo_in_dwp (struct dwp_file *dwp_
(fewer struct dwo_file objects to allocated). Remember that for
really
large apps there can be on the order of 8K CUs and 200K TUs, or more.
*/
- xasprintf (&virtual_dwo_name, "virtual-dwo/%d-%d-%d-%d",
- sections.abbrev.asection ? sections.abbrev.asection->id : 0,
- sections.line.asection ? sections.line.asection->id : 0,
- sections.loc.asection ? sections.loc.asection->id : 0,
- (sections.str_offsets.asection
- ? sections.str_offsets.asection->id
- : 0));
+ virtual_dwo_name =
+ xstrprintf ("virtual-dwo/%d-%d-%d-%d",
+ sections.abbrev.asection ? sections.abbrev.asection->id : 0,
+ sections.line.asection ? sections.line.asection->id : 0,
+ sections.loc.asection ? sections.loc.asection->id : 0,
+ (sections.str_offsets.asection
+ ? sections.str_offsets.asection->id
+ : 0));
make_cleanup (xfree, virtual_dwo_name);
/* Can we use an existing virtual DWO file? */
dwo_file_slot = lookup_dwo_file_slot (virtual_dwo_name);
@@ -8981,7 +8982,7 @@ open_and_init_dwp_file (const char *comp
bfd *dbfd;
struct cleanup *cleanups;
- xasprintf (&dwp_name, "%s.dwp", dwarf2_per_objfile->objfile->name);
+ dwp_name = xstrprintf ("%s.dwp", dwarf2_per_objfile->objfile->name);
cleanups = make_cleanup (xfree, dwp_name);
dbfd = open_dwop_file (dwp_name, comp_dir, 1);
next prev parent reply other threads:[~2012-11-06 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 1:59 GDB Administrator
2012-11-06 11:08 ` Pierre Muller [this message]
[not found] ` <5098efb2.05fd440a.7696.ffffd821SMTPIN_ADDED@mx.google.com>
2012-11-06 19:02 ` [RFA] Fix " Pedro Alves
2012-11-12 9:17 ` PING: " Pierre Muller
2012-11-12 15:51 ` Joel Brobecker
2012-11-12 16:01 ` Pierre Muller
2012-11-12 16:28 ` Tom Tromey
[not found] ` <22453.3111825169$1352736109@news.gmane.org>
2012-11-12 16:29 ` Tom Tromey
2012-11-12 17:06 ` Joel Brobecker
[not found] ` <40242.9794231013$1352711862@news.gmane.org>
2012-11-14 16:45 ` Tom Tromey
2012-11-15 8:14 ` Pierre Muller
2012-11-15 8:32 ` Pierre Muller
[not found] ` <50a4a88c.47f0440a.4029.ffff805aSMTPIN_ADDED@mx.google.com>
2012-11-15 11:36 ` Pedro Alves
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='007101cdbc0f$07a68fa0$16f3aee0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=devans@sourceware.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