From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: FYI: Ada results on Debian/unstable
Date: Wed, 23 Jan 2008 13:15:00 -0000 [thread overview]
Message-ID: <20080123131442.GA32621@caradoc.them.org> (raw)
I haven't run the GDB testsuite in a while. Here's the new test failures
since I last did. I suspect these all rely on debug info that the
latest AdaCore tree generates that a relatively recent (4.1-based)
FSF gnat does not.
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/array_bounds.exp ...
+PASS: gdb.ada/array_bounds.exp: print itable'first
+PASS: gdb.ada/array_bounds.exp: print itable'last
+FAIL: gdb.ada/array_bounds.exp: print table'first
+FAIL: gdb.ada/array_bounds.exp: print table'last
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/arrayparam.exp ...
+FAIL: gdb.ada/arrayparam.exp: print call_me ("bonjour")
+FAIL: gdb.ada/arrayparam.exp: print first after function call
+FAIL: gdb.ada/arrayparam.exp: print lasta after function call
+FAIL: gdb.ada/arrayparam.exp: print length after function call
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/char_param.exp ...
+FAIL: gdb.ada/char_param.exp: print procedure_result before calling same
+PASS: gdb.ada/char_param.exp: call same
+FAIL: gdb.ada/char_param.exp: print procedure_result after calling same
+FAIL: gdb.ada/char_param.exp: call next
+FAIL: gdb.ada/char_param.exp: print procedure_result after calling next
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/frame_args.exp ...
+PASS: gdb.ada/frame_args.exp: set print frame-arguments scalars
+FAIL: gdb.ada/frame_args.exp: display frame 1 with frame-arguments set to scalars
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/funcall_param.exp ...
+FAIL: gdb.ada/funcall_param.exp: p ident (ident (my_parameter))
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/homonym.exp ...
+PASS: gdb.ada/homonym.exp: ptype local_type at BREAK_1
+FAIL: gdb.ada/homonym.exp: ptype local_type_subtype at BREAK_1
+FAIL: gdb.ada/homonym.exp: ptype int_type at BREAK_1
+PASS: gdb.ada/homonym.exp: ptype lcl at BREAK_1
+PASS: gdb.ada/homonym.exp: print lcl at BREAK_1
+PASS: gdb.ada/homonym.exp: break at BREAK_2
+PASS: gdb.ada/homonym.exp: continue until BREAK_2
+PASS: gdb.ada/homonym.exp: ptype local_type at BREAK_2
+FAIL: gdb.ada/homonym.exp: ptype local_type_subtype at BREAK_2
+PASS: gdb.ada/homonym.exp: ptype lcl at BREAK_2
+PASS: gdb.ada/homonym.exp: print lcl at BREAK_2
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/interface.exp ...
+PASS: gdb.ada/interface.exp: print r
+FAIL: gdb.ada/interface.exp: print s (GDB internal error)
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/null_array.exp ...
+PASS: gdb.ada/null_array.exp: print my_table
+FAIL: gdb.ada/null_array.exp: ptype my_table
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2008-01-23 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 13:15 Daniel Jacobowitz [this message]
2008-01-23 13:16 ` Daniel Jacobowitz
2008-01-23 18:47 ` Joel Brobecker
2008-01-23 18:53 ` Daniel Jacobowitz
2008-01-24 0:31 ` 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=20080123131442.GA32621@caradoc.them.org \
--to=drow@false.org \
--cc=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