Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] AR Index: Add exceptions for gnulib/string.in.h
Date: Mon, 23 Mar 2009 23:14:00 -0000	[thread overview]
Message-ID: <000701c9ac0a$0ad213c0$20763b40$@u-strasbg.fr> (raw)

2 strdup and 2 strerror failures listed in
AR Index are due to code in gnulib/string.in.h
header.

  This code inserts a linking time warning
so I suppose that it can be added to the list of 
occurrences that can be ignored.

Commit log:
	* Add exceptions for gnulib/string.in.h
	for 2 strdup and 2 strerror occurrences.

Is this OK?


Pierre Muller
Pascal language support maintainer for GDB



Index: gdb_ari.sh
===================================================================
RCS file: /cvs/gdbadmin/ss/gdb_ari.sh,v
retrieving revision 1.80
diff -u -p -r1.80 gdb_ari.sh
--- gdb_ari.sh  23 Mar 2009 14:38:19 -0000      1.80
+++ gdb_ari.sh  23 Mar 2009 22:46:00 -0000
@@ -498,6 +498,7 @@ Do not use &&, or || at the end of a lin
 BEGIN { doc["strerror"] = "\
 Do not use strerror(), instead use safe_strerror()"
     category["strerror"] = ari_regression
+    fix("strerror", "gdb/gnulib/string.in.h", 2)
     fix("strerror", "gdb/gdb_string.h", 1)
     fix("strerror", "gdb/mingw-hdep.c", 1)
     fix("strerror", "gdb/posix-hdep.c", 1)
@@ -1336,6 +1337,7 @@ Do not use strdup(), instead use xstrdup
     category["strdup"] = ari_regression
 }
 /(^|[^_[:alnum:]])strdup[[:space:]]*\(/ {
+    fix("strdup", "gdb/gnulib/string.in.h", 2)
     fail("strdup")
 }



             reply	other threads:[~2009-03-23 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 23:14 Pierre Muller [this message]
2009-03-23 23:36 ` Joel Brobecker
2009-03-24  0:00   ` Pierre Muller
2009-03-24  2:44     ` Joel Brobecker
2009-03-24  7:22       ` [PATCH] AR Index: Ignore gnulib directory Pierre Muller
2009-03-24  1:27   ` [RFA] AR Index: Add exceptions for gnulib/string.in.h Tom Tromey

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='000701c9ac0a$0ad213c0$20763b40$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --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