From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13610 invoked by alias); 20 Jul 2009 13:02:17 -0000 Received: (qmail 13584 invoked by uid 22791); 20 Jul 2009 13:02:13 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 20 Jul 2009 13:02:01 +0000 Received: (qmail 12819 invoked from network); 20 Jul 2009 13:02:00 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 20 Jul 2009 13:02:00 -0000 From: Pedro Alves To: Doug Evans Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings. Date: Mon, 20 Jul 2009 13:21:00 -0000 User-Agent: KMail/1.9.10 Cc: Eli Zaretskii , tromey@redhat.com, gdb-patches@sourceware.org References: <20090523232414.BED2B846C2@localhost> <200907022344.12495.pedro@codesourcery.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907201402.47393.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: 2009-07/txt/msg00470.txt.bz2 [sorry for the delay, I'd been AFK] On Friday 10 July 2009 23:12:19, Doug Evans wrote: > The attached patch adds an optional regex argument to "info shared" > and marks in the output libraries without debugging info. > With this addition, I don't see a real need for a "set print > symbol-loading-warning/whatever" option, thus I deleted it. > > Ok to check in? > I like this approach better. I like the regex consistency with "sharedlibrary". I'm not sure if a '(*)' is the best UI, compared to an explicit word, though, but I can live with it if others can too. What do others think? Also, did you have a chance to run this through your users? Did you try this with any frontend? I've now realized that MI clients are probably parsing "info sharedlibrary" output for lack for an equivalent MI command. :-/ :-( -- Pedro Alves