Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] ada testsuite: False FAILs with gcc debug info
Date: Mon, 28 Mar 2011 20:21:00 -0000	[thread overview]
Message-ID: <20110328200825.GA22355@host1.jankratochvil.net> (raw)
In-Reply-To: <20110328165022.GB3670@adacore.com>

On Mon, 28 Mar 2011 18:50:22 +0200, Joel Brobecker wrote:
> Just a thought: Perhaps it might be easier to flip runtimes if you
> provide the runtime with debug info as a second runtime.  There is
> a way to do this, and then the user controls which one he wants using
> --RTS=<rts-name> (only when the default one is not the one he wants).

I do not understand this much.  I have the single system only compiler, which
also provides debug info for all its parts.  While I can have some special GCC
builds still with the default system compiler the GDB testsuite should work.


> This is incorrect, but I cannot reproduce (we should be able to get
> the same behavior by recompiling the program with "-f -a", which tells
> gnatmake to recompile everything, including runtime files).

`gnatmake -f -a -g foo' works but it gives the same results for me.


> And type Character_Set does not match type String:

It does match:

(gdb) set language c
(gdb) ptype ada__strings__maps__Oeq
type = boolean (ada__strings__maps__character_set___XP1 &, ada__strings__maps__character_set___XP1 &)
(gdb) set language auto
(gdb) ptype ada.strings.maps.character_set
type = array (character) of boolean <packed: 1-bit elements>
(gdb) ptype "a"
type = array (1 .. 1) of character

and ada_type_match for TYPE_CODE_ARRAY returns 1 without checking whether the
array's target type matches.  And both these types are arrays.  Why
Character_Set should not match String with this ada_type_match implementation?


> I think the debugging info must be incorrect.

So far it seems to me ada_type_match has a bug, does not it?


> > gdb/testsuite/
> > 2011-03-27  Jan Kratochvil  <jan.kratochvil@redhat.com>
> > 
> > 	* gdb.ada/arrayparam.exp (print first after function call): Use
> > 	explicit package name.  Add a comment
> > 	(print lasta after function call): Rename ...
> > 	(print last after function call): ... it and use explicit package
> > 	name.
> > 	(print length after function call): Use explicit package name.
> > 	* gdb.ada/str_ref_cmp.exp (operator = works for strings): New test.
> > 	* gdb.ada/sym_print_name.exp: Change `i' to `integervar'.
> > 	(multiple matches for symbol i): Rename ...
> > 	(multiple matches for symbol integervar): ... it.
> > 	* gdb.ada/sym_print_name/foo.adb (Foo): Change `I' to `IntegerVar'.
> > 	* gdb.ada/sym_print_name/pck.ads (Pck): Likewise.
> 
> This is OK.

Therefore checked in so that it no longer occasionally gives false
regressions.
	http://sourceware.org/ml/gdb-cvs/2011-03/msg00308.html


Thanks,
Jan


  parent reply	other threads:[~2011-03-28 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  8:06 Jan Kratochvil
2011-03-28 18:05 ` Joel Brobecker
2011-03-28 18:46   ` Tom Tromey
2011-03-28 20:21   ` Jan Kratochvil [this message]
2011-03-28 21:27     ` Joel Brobecker

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=20110328200825.GA22355@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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