From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6797 invoked by alias); 9 Feb 2009 22:17:05 -0000 Received: (qmail 6785 invoked by uid 22791); 9 Feb 2009 22:17:04 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,SARE_RAND_1,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, 09 Feb 2009 22:16:58 +0000 Received: (qmail 664 invoked from network); 9 Feb 2009 22:16:56 -0000 Received: from unknown (HELO orlando) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 9 Feb 2009 22:16:56 -0000 From: Pedro Alves To: Paul Pluzhnikov Subject: Re: [2/2] Inspect extra signal information Date: Mon, 09 Feb 2009 22:17:00 -0000 User-Agent: KMail/1.9.10 Cc: gdb-patches@sourceware.org References: <200901121846.51709.pedro@codesourcery.com> <200902062335.17737.pedro@codesourcery.com> <8ac60eac0902082223q2192830cu8b75f6424fca6c68@mail.gmail.com> In-Reply-To: <8ac60eac0902082223q2192830cu8b75f6424fca6c68@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902092216.54762.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-02/txt/msg00209.txt.bz2 On Monday 09 February 2009 06:23:36, Paul Pluzhnikov wrote: > On Fri, Feb 6, 2009 at 3:35 PM, Pedro Alves wrote: > > Here's the version of this patch that went in. > > AFAICT, this broke 'gdb.base/default.exp' show convenience, > which expects "No debugger convenience variables ..." > Sigh. I don't know how, but I somehow missed this one all along. I suspect I was comparing testresults with a log that already had the problem. I'll try to make sure it doesn't happen again. > Instead, it gets: > > $ ./gdb -nx > GNU gdb (GDB) 6.8.50.20090207-cvs > ... > This GDB was configured as "x86_64-unknown-linux-gnu". > For bug reporting instructions, please see: > . > (gdb) show convenience > $_siginfo = void > (gdb) > > I find it weird to have a "void" $_siginfo ... > That's what you get for all other convenience variables when they are empty: E.g.: >gdb-6.8 (gdb) p $_siginfo $1 = void Or: >gdb-6.8 (gdb) p $randomvar $1 = void (gdb) show convenience $randomvar = void I'm not 100% sure if we want to fix this, or if we want to adjust the testsuite instead, and making clear in the docs that the variable can be empty. We could try delaying creating the convenience variable a bit, but, how much? First stop? --- there's targets that could in principle show extra signal information without a stop (opening a core, or, opening a remote-ish target (ignore start_remote, please)). First target push (not the exec target though) ? --- sounds like a bit of a hack. Grumble. -- Pedro Alves