From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1062 invoked by alias); 29 May 2009 12:07:07 -0000 Received: (qmail 1045 invoked by uid 22791); 29 May 2009 12:07:05 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout3.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 May 2009 12:07:01 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KKE00400MZ7D200@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Fri, 29 May 2009 15:06:58 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.115.215]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KKE00HT2MZMPV80@i_mtaout3.012.net.il>; Fri, 29 May 2009 15:06:58 +0300 (IDT) Date: Fri, 29 May 2009 12:07:00 -0000 From: Eli Zaretskii Subject: Re: [RFA] Fix printing frame arguments for COFF debug info In-reply-to: <20090525225537.GH23016@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83skio3yft.fsf@gnu.org> References: <83d4a9q9e5.fsf@gnu.org> <20090520213200.GE16152@adacore.com> <837i0bp2bb.fsf@gnu.org> <20090521170502.GJ16152@adacore.com> <83iqjst89t.fsf@gnu.org> <20090525062922.GE23016@adacore.com> <83ws84syok.fsf@gnu.org> <20090525225537.GH23016@adacore.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-05/txt/msg00622.txt.bz2 > Date: Mon, 25 May 2009 15:55:37 -0700 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > > We're trying to recover nicely from the situation in order to be > > > more useful for the user, so getting rid of the error is OK, but I'd > > > probably still emit a complaint. WDYT? > > > > How about a warning under verbose operation? Would that be enough? > > Sure. I don't know what the verbose switch would be I thought about info_verbose. > I believe that complaints provide that kind of functionality - by > default, complaints are turned off, but you can configure GDB to > print the first N complaints emitted. I looked into this, and I don't see a way to display a complaint in this context. The problem is that val_print is called a lot in the middle of displaying arguments to functions, where a non-fatal warning message cannot be reasonably displayed, especially if the message is long. Perhaps I'm missing something, but I don't see any machinery in complaints.c (or elsewhere, for that matter) to handle such situations.