From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21870 invoked by alias); 25 Jul 2012 15:30:12 -0000 Received: (qmail 21833 invoked by uid 22791); 25 Jul 2012 15:30:11 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 Jul 2012 15:29:58 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0EE081C6B35; Wed, 25 Jul 2012 11:29:54 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id naEbn8-yhpNp; Wed, 25 Jul 2012 11:29:53 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D4E0E1C6A33; Wed, 25 Jul 2012 11:29:53 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 3654114561A; Wed, 25 Jul 2012 08:29:48 -0700 (PDT) Date: Wed, 25 Jul 2012 15:30:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: New ARI warning Sun Jul 8 01:55:37 UTC 2012 Message-ID: <20120725152948.GC24718@adacore.com> References: <20120708015538.GA10693@sourceware.org> <20120708085302.GA4153@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120708085302.GA4153@host2.jankratochvil.net> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-07/txt/msg00540.txt.bz2 > safe_strerror has the same problem for gdbserver. > > As this is all in Linux-only and even i386-only code I find it both safe. > glibc both accepts NULL for %s and produces "Unknown error 324234234" for > invalid errno. Also errno is there only the system produced one. > I am not aware of non-glibc libcs behavior but it should not be problem. If the uses are approved, can we mark them as such, so that they disappear from the ARI? IIRC, the procedure for doing that is to add /* ARI: */. -- Joel