From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23259 invoked by alias); 28 Jul 2010 18:16:24 -0000 Received: (qmail 23248 invoked by uid 22791); 28 Jul 2010 18:16:23 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Jul 2010 18:16:17 +0000 Received: (qmail 17054 invoked from network); 28 Jul 2010 18:16:16 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 28 Jul 2010 18:16:16 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: New ARI warning Fri Jul 2 01:53:49 UTC 2010 Date: Wed, 28 Jul 2010 18:16:00 -0000 User-Agent: KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; x86_64; ; ) Cc: Joel Brobecker References: <20100702015349.GA10024@sourceware.org> <20100728180731.GS13267@adacore.com> In-Reply-To: <20100728180731.GS13267@adacore.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201007281916.13404.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2010-07/txt/msg00505.txt.bz2 On Wednesday 28 July 2010 19:07:31, Joel Brobecker wrote: > > > gdb/remote.c:2787: code: sprintf: Do not use sprintf, instead use xstrprintf > > gdb/remote.c:2787: sprintf (p, '); > > 1161a1163 > > > gdb/remote.c:9747: gettext: _ markup: All messages should be marked up with _. > > gdb/remote.c:9747: error ("Static tracepoint not valid during download"); > > 1450,1451d1451 > > > gdb/tracepoint.c:4133: gettext: _ markup: All messages should be marked up with _. > > gdb/tracepoint.c:4133: error ("bad marker definition: %s", line); > > I fixed those thusly. I don't know how to say this without sounding > like I am complaining, but I had hoped that we would all look at those > reports and that whoever caused the new warnings would act to fix them. Sounds like my fault. Sorry, I completely missed this. Do fell free to just bring it to my attention to fix it instead of fixing it yourself. :-) Thanks for fixing. -- Pedro Alves