Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: arrayidx.exp failures
Date: Fri, 13 Oct 2006 02:38:00 -0000	[thread overview]
Message-ID: <20061013023839.GI1059@adacore.com> (raw)
In-Reply-To: <17710.63085.830960.73093@kahikatea.snap.net.nz>

> 2006-10-06  Joel Brobecker  <brobecker@adacore.com>
> 
> 	* gdb.ada/arrayidx.exp: Remove calls to setup_kfail now that
> 	the corresponding bug has been fixed in GDB (PR/2018).
> 
> They still fail for me with:
> 
> GNU gdb 6.5.50.20061013-cvs
> This GDB was configured as "i686-pc-linux-gnu".
> 
> I can't see any mention of PR/2018 in gdb/ChangeLog.  Has this fix actually
> been committed?

Yes: 

2006-10-06 Joel Brobecker  <brobecker@adacore.com>

        * dwarf2read.c (read_array_type): Set the type name if the name
        attribute is present.

I will add a mention of the PR in the changelog, that's a good remark.

In terms of why it fails for you, it is probably because of something
else. I will guess that you are missing some parts of the encodings
necessary to complete the decoding of the array. The encoding is
documented in ada/exp_dbug.ads of GCC. So I'm guessing a malfunction
of GCC rather than a possible bug in GDB.

We're pushing all the changes we made for 41 in that department as fast
as we can so that everyone can enjoy the most of Ada. But long term,
we'll be moving towards pure dwarf data.

-- 
Joel


  reply	other threads:[~2006-10-13  2:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  2:17 Nick Roberts
2006-10-13  2:38 ` Joel Brobecker [this message]
2006-10-13  4:39   ` Daniel Jacobowitz
2006-10-13 16:34     ` Joel Brobecker
2006-10-13 18:50       ` Nick Roberts
2006-10-13 20:10         ` Joel Brobecker
2006-10-13 22:06       ` Daniel Jacobowitz

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=20061013023839.GI1059@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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