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 07:37:00 -0000	[thread overview]
Message-ID: <20070102073827.GB3434@adacore.com> (raw)
In-Reply-To: <20061231194604.GA23919@nevyn.them.org>

> Joel, I have seen Ada testsuite failures on GNU/Linux for about as long
> as we've had tests.  Do you know the status of these tests when run
> against FSF releases of gnat, rather than the AdaCore version?

I don't work at all with the FSF release of GCC, only with the AdaCore one.

> I suspect it's inadequate debug info.

I wouldn't be surprised. Recents versions of GCC are much better at
not emitting debugging info for unused entity. This has caused us a lot
of trouble when moving to GCC 4.1 for instance, because GNAT generates
of lot of entities that appear unused from the compiler point of view,
but are necessary for the debugger to work properly. We're getting back
to the same project of getting rid of all these encoding in favor of
standard DWARF. This is actually a very active project that we're
working on right now, so hopefully the situation won't be as bad soon.

I can ask that the local patches we maintain in our tree be submitted
for inclusion if you think they'd be accepted. Our opinion was that they
would probably be rejected as a step backward.

> print e_one_two_three
> $2 = (0 => 1, 2, 3)

In this case, for instance, you are probably missing the debugging
info for a type named: p__etable___XA. If you have a look at exp_dbug.ads
in the compiler sources, this is what we call a parallel type which
contains one field. The name of the field is the name of array index type.  

Not very elegant, but necessary in many cases when the platform does not
support stabs.

> print p_one_two_three
> $4 = warning: could not find bounds information on packed array
> can't unpack array
> 
> (gdb) FAIL: gdb.ada/arrayidx.exp: print p_one_two_three, indexes off

This case is probably the same sort of issue. I looked at the sources
and it looks like GDB did not find the parallel type correspoinding
to this array. The parallel type is computed by stripping the ___XP
suffix in the type name (in this case, it looks like GDB failed to
find type p__ptable.

> ptype empty
> type = function return int
> (gdb) FAIL: gdb.ada/null_record.exp: ptype on null record

Strangely, I just noticed that I have the same failure on my side.
I will investigate.

> $1 = warning: could not find bounds information on packed array
> can't unpack array
> 
> (gdb) FAIL: gdb.ada/packed_array.exp: print var

This is probably the same as the packed array case above.

-- 
Joel


  reply	other threads:[~2007-01-02  7:37 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 [this message]
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
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=20070102073827.GB3434@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