Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: Ada testsuite failures
Date: Tue, 02 Jan 2007 16:30:00 -0000	[thread overview]
Message-ID: <20070102163108.GJ3434@adacore.com> (raw)
In-Reply-To: <20070102143926.GA10771@nevyn.them.org>

> (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.

Yes and no. The test isn't representative of "real code". It will
be more productive to enhance the testcase a bit, I was very naive
when I wrote this code - it must have been the reduced testcase
I have been using to track down the issue, the code we have in our
testsuite is a bit better that way.

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

Yes, I agree. Could you try the following patch?

2006-01-02  Joel Brobecker  <brobecker@adacore.com>

	* gdb.ada/null_record/bar.ads (Do_Nothing): Add extra parameter.
	* gdb.ada/null_record/bar.adb (Do_Nothing): Likewise.
	* gdb.ada/null_record/null_record.adb: Fake use of type Empty
	to prevent this type from being optimized out.

That should help,
-- 
Joel


  reply	other threads:[~2007-01-02 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 19:46 Daniel Jacobowitz
2007-01-02  7:37 ` Joel Brobecker
2007-01-02 14:42   ` Daniel Jacobowitz
2007-01-02 16:31     ` Joel Brobecker
2007-01-02 11:38 ` Joel Brobecker
2007-01-02 14:39   ` Daniel Jacobowitz
2007-01-02 16:30     ` Joel Brobecker [this message]
2007-01-02 16:32       ` Joel Brobecker
2007-01-02 16:40         ` Daniel Jacobowitz
2007-01-02 16:50           ` Joel Brobecker
2007-01-03 14:04           ` Joel Brobecker
2007-01-03 14:05             ` Joel Brobecker
2007-01-03 22:21             ` Jim Blandy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070102163108.GJ3434@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox