From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24950 invoked by alias); 2 Jan 2007 11:38:24 -0000 Received: (qmail 24940 invoked by uid 22791); 2 Jan 2007 11:38:24 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 02 Jan 2007 11:38:18 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 74B4B48CEA1 for ; Tue, 2 Jan 2007 06:38:16 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02697-01-3 for ; Tue, 2 Jan 2007 06:38:16 -0500 (EST) Received: from takamaka.act-europe.fr (AStDenis-105-1-58-225.w80-8.abo.wanadoo.fr [80.8.155.225]) by nile.gnat.com (Postfix) with ESMTP id D9EF848CCBF for ; Tue, 2 Jan 2007 06:38:15 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 5018A34C099; Tue, 2 Jan 2007 15:39:03 +0400 (RET) Date: Tue, 02 Jan 2007 11:38:00 -0000 From: Joel Brobecker To: gdb@sourceware.org Subject: Re: Ada testsuite failures Message-ID: <20070102113903.GH3434@adacore.com> References: <20061231194604.GA23919@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061231194604.GA23919@nevyn.them.org> User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00009.txt.bz2 Daniel, > ptype empty > type = function return int > (gdb) FAIL: gdb.ada/null_record.exp: ptype on null record My appologies when I said I had the same failure. I do have a failure, but the symptoms are different. What does the debugger print in your case when you do: (gdb) ptype bar.empty Can you perhaps cd to testsuite/gdb.ada/null_record, do the following: % gnatmake -f -g null_record -cargs -dA -save-temps Then tar up the null_record directory and send it to me. I should be able to tell you whether it's a debugging information issue or something else. Thanks you, -- Joel