Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <palves@redhat.com>
Cc: <devans@sourceware.org>, <gdb-patches@sourceware.org>
Subject: PING: [RFA] Fix New ARI warning Tue Nov  6 01:58:48 UTC 2012
Date: Mon, 12 Nov 2012 09:17:00 -0000	[thread overview]
Message-ID: <001b01cdc0b6$7e7b67d0$7b723770$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <50995EBB.6070503@redhat.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : mardi 6 novembre 2012 20:02
> À : Pierre Muller
> Cc : devans@sourceware.org; gdb-patches@sourceware.org
> Objet : Re: [RFA] Fix New ARI warning Tue Nov 6 01:58:48 UTC 2012
> 
> On 11/06/2012 11:08 AM, Pierre Muller wrote:
> 
> >> 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

  Doug didn't reply yet to this RFA...
 
> Déjà vu :-)
> 
> http://sourceware.org/ml/gdb-patches/2009-03/msg00576.html
> 
> This removes the last use of xasprintf in the tree; we should delete
> it to avoid new uses creeping in.

  There is probably a list of other similar functions
that we should obsolete.
  The main question is, should we do it brutally
or softly.

  1-- Brutal method:
Remove function from both header and C sources
as well as from ARI script.


  2 -- Soft method:
Start by simply removing function from header.
Change function to static.
Wait for one release and suppress completely.

  Method 1 is simpler, but
not adapted to some functions that are used internally.
  Method 2 is gentler to outsiders using gdb sources for
external projects, like the inclusion of libgdb.a into
the Free Pascal IDE, which I basically try to maintain...
Yes, I know I should be using mi, but I never got to 
switch :(

Pierre Muller 
as ARI maintainer




  reply	other threads:[~2012-11-12  9:17 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 ` [RFA] Fix " Pierre Muller
     [not found] ` <5098efb2.05fd440a.7696.ffffd821SMTPIN_ADDED@mx.google.com>
2012-11-06 19:02   ` Pedro Alves
2012-11-12  9:17     ` Pierre Muller [this message]
2012-11-12 15:51       ` PING: " 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='001b01cdc0b6$7e7b67d0$7b723770$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=devans@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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