From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31456 invoked by alias); 5 Mar 2012 21:55:04 -0000 Received: (qmail 31192 invoked by uid 22791); 5 Mar 2012 21:55:02 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 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; Mon, 05 Mar 2012 21:54:49 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id AEC951C6545; Mon, 5 Mar 2012 16:54:48 -0500 (EST) 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 vDgR3e+53Qeu; Mon, 5 Mar 2012 16:54:48 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 76A671C64B7; Mon, 5 Mar 2012 16:54:47 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 7382E145615; Mon, 5 Mar 2012 13:54:45 -0800 (PST) Date: Mon, 05 Mar 2012 21:55:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sourceware.org Subject: Re: RFA: two Ada tests -vs- debug-file-directory Message-ID: <20120305215445.GL2853@adacore.com> References: <87y5revka9.fsf@fleche.redhat.com> <20120305210413.GK2853@adacore.com> <87ipiivj5s.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ipiivj5s.fsf@fleche.redhat.com> 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-03/txt/msg00165.txt.bz2 > I've attached gdb.log for a failing run of the two tests. Thank you! For the first test (mi_task_arg.exp), the failure is indeed caused by the fact that a function in the callstack for which there is normally no debugging info (and thus no parameters in the backtrace) now has debug info, and starts showing parameters for that frame. Your fix prevents that from happening, and is just as good as allowing the parameters in the output from the -stack-list-arguments command. For the second testcase, the debugger picks up a wack load of functions that fit the profile of a function we are trying to break into (Ada operator "+", for instance). So we end up with more locations than we expected. The fix you provided is the only reasonable fix in this case. So I wouldn't change a thing :). -- Joel