From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-27262-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27285 invoked by alias); 2 Jan 2007 14:39:34 -0000
Received: (qmail 27275 invoked by uid 22791); 2 Jan 2007 14:39:34 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)     by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 02 Jan 2007 14:39:28 +0000
Received: from drow by nevyn.them.org with local (Exim 4.63) 	(envelope-from <drow@nevyn.them.org>) 	id 1H1knW-0002ps-D9 	for gdb@sourceware.org; Tue, 02 Jan 2007 09:39:26 -0500
Date: Tue, 02 Jan 2007 14:39:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Ada testsuite failures
Message-ID: <20070102143926.GA10771@nevyn.them.org>
Mail-Followup-To: gdb@sourceware.org
References: <20061231194604.GA23919@nevyn.them.org> <20070102113903.GH3434@adacore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070102113903.GH3434@adacore.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-01/txt/msg00010.txt.bz2

On Tue, Jan 02, 2007 at 03:39:03PM +0400, Joel Brobecker wrote:
> 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

(gdb) ptype empty
type = function return int

(gdb) p bar.empty
No definition of "bar.empty" in current context.

(gdb) p empty
$1 = {<text variable, no debug info>} 0x2aaaaad3d590 <gnat__sockets__empty>

Isn't that interesting - that's something completely different.  There
are zero references to the string "empty" in the debug info for
null_record, so it is definitely a debugging information problem.

Looking at the test I'm not surprised.  Empty is unused; adding
something that references it is probably sufficient.

-- 
Daniel Jacobowitz
CodeSourcery