FYI: Ada results on Debian/unstable

FYI: Ada results on Debian/unstable

[Daniel Jacobowitz]

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

Re: FYI: Ada results on Debian/unstable

[Daniel Jacobowitz]

On Wed, Jan 23, 2008 at 08:14:42AM -0500, Daniel Jacobowitz wrote:
> +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

Whoops, stopped too early.

 Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/packed_array.exp  ...
 FAIL: gdb.ada/packed_array.exp: print var
+FAIL: gdb.ada/packed_array.exp: ptype &var
+ERROR: Process no longer exists
+UNRESOLVED: gdb.ada/packed_array.exp: print &var
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/packed_tagged.exp ...
+FAIL: gdb.ada/packed_tagged.exp: print x (GDB internal error)
+FAIL: gdb.ada/packed_tagged.exp: ptype x (GDB internal error)
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/print_chars.exp ...
+FAIL: gdb.ada/print_chars.exp: print C
+FAIL: gdb.ada/print_chars.exp: print WC
+FAIL: gdb.ada/print_chars.exp: print WWC
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/str_ref_cmp.exp ...
+FAIL: gdb.ada/str_ref_cmp.exp: print String_Var (1 .. 3) = "Hel"
+FAIL: gdb.ada/str_ref_cmp.exp: print String_Var (1 .. 3) = "hel"
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/taft_type.exp ...
+PASS: gdb.ada/taft_type.exp: print w.e.all
+Running /space/fsf/commit/src/gdb/testsuite/gdb.ada/tagged.exp ...
+PASS: gdb.ada/tagged.exp: ptype segm
+PASS: gdb.ada/tagged.exp: print segm
+FAIL: gdb.ada/tagged.exp: ptype obj (GDB internal error)
+FAIL: gdb.ada/tagged.exp: print obj (GDB internal error)

-- 
Daniel Jacobowitz
CodeSourcery

Re: FYI: Ada results on Debian/unstable

[Joel Brobecker]

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

Yes, this is most probably the cause of these failures. I would guess
that fixes related to debug-info don't get ported to the 4.1 branch.
To be verified.

I just installed the Debian version of GNAT, but I'm running "testing"
not unstable. I do see the failures, and I was going to look into the
internal errors, but I don't get those with the version of GNAT I
installed. Are the errors a problem for Debian?

More interesting would be to run the testsuite with HEAD GCC.
I'll try to do that when I have a minute (I just arrived yesterday
night after a 36h trip).

-- 
Joel

Re: FYI: Ada results on Debian/unstable

[Daniel Jacobowitz]

On Wed, Jan 23, 2008 at 10:47:10AM -0800, Joel Brobecker wrote:
> I just installed the Debian version of GNAT, but I'm running "testing"
> not unstable. I do see the failures, and I was going to look into the
> internal errors, but I don't get those with the version of GNAT I
> installed. Are the errors a problem for Debian?

Nope.  Just annoying to me, but now that I have a new baseline, it's
no big deal.

The internal errors all look like:

(gdb) print r
$1 = (x => 1, y => 2, w => 3, h => 4)
(gdb) PASS: gdb.ada/interface.exp: print r
print s
/space/fsf/commit/src/gdb/utils.c:904: internal-error: virtual memory
exhausted: can't allocate 4294967423 bytes.
A problem internal to GDB has been detected,

Breakpoint 1, comp_bug () at
/space/fsf/commit/src/gdb/testsuite/gdb.ada/packed_tagged/comp_bug.adb:37
37         if X.Exists then -- STOP
(gdb) print x
/space/fsf/commit/src/gdb/utils.c:904: internal-error: virtual memory
exhausted: can't allocate 4294967423 bytes.
A problem internal to GDB has been detected,


-- 
Daniel Jacobowitz
CodeSourcery

Re: FYI: Ada results on Debian/unstable

[Joel Brobecker]

> Nope.  Just annoying to me, but now that I have a new baseline, it's
> no big deal.

Good to know that you can work with a baseline.  I'm not sure there
is much we can do to help. I looked at the GCC web pages, and even if
we wanted to, I don't think that we'll be able to push any changes
to the 4.1 branch.  What I can say is that I'm regularly monitoring
the Ada testcases by running them and making sure that none of them
regress (but that's with the AdaCore compiler, though, as I very very
rarely build my own compiler). I don't think that it's a big deal
if you decide to always ignore failures inside gdb.ada.

I think that Eric Botcazou and Olivier Hainque are particularly
diligent at submitting GCC backend changes for AdaCore, and Arno
Charlet should be taking care of all the front-end changes.
So we should converge at some point.

> (gdb) print r
> $1 = (x => 1, y => 2, w => 3, h => 4)
> (gdb) PASS: gdb.ada/interface.exp: print r
> print s
> /space/fsf/commit/src/gdb/utils.c:904: internal-error: virtual memory
> exhausted: can't allocate 4294967423 bytes.
> A problem internal to GDB has been detected,

That could indeed be related to bad debugging info.

-- 
Joel