[RFA/testsuite/ada] Refine expected output of start command
Thu Oct 21 03:38:00 GMT 2004
On Wed, Oct 20, 2004 at 07:49:15PM -0700, Joel Brobecker wrote:
> While refreshing my memory on how the start command is implemented,
> I found that it would currently only work with stabs. This concerns
> Ada only, as this is the only language that I remember of that has
> a main procedure name that's different from "main".
> Anyway, so I checked out the results of gdb.ada/null_record.exp which
> I thought were an all PASS. And it is. It's just that the regexp
> used to match the expected output is not stringent enough. Basically,
> since the current mechanism doesn't work with dwarf2, GDB sets the
> temporary breakpoint inside "main", rather than "null_record".
> So we get this output:
Actually, it's been failing for me for a maybe related reason:
Breakpoint 1 at 0x8048ad0: file b~null_record.adb, line 99.
Starting program: /opt/src/binutils/x86-as/gdb/testsuite/gdb.ada/null_record
main (argc=1, argv=(system.address) 0xbffff524, envp=(system.address) 0xbffff52c) at b~null_record.adb:99
99 Ensure_Reference : System.Address :=
(gdb) PASS: gdb.ada/null_record.exp: start
type = function return int
(gdb) FAIL: gdb.ada/null_record.exp: ptype on null record
> 2004-10-20 Joel Brobecker <firstname.lastname@example.org>
> * gdb.ada/null_record.exp: Check where we stopped after
> sending the start command, instead of where the associated
> temporary breakpoint was inserted.
> This causes the "start" test above to FAIL for now. But the fix for
> this should be available soon.
> OK to commit? (I verified that this PASSes again once I apply my fix)
This is OK.
More information about the Gdb-patches