This is the mail archive of the
gdb-testers@sources.redhat.com
mailing list for the GDB project.
gdb 6.0.92, native hppa2.0w-hp-hpux11.11
- From: mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)
- To: gdb-testers at sources dot redhat dot com
- Date: Sun, 4 Apr 2004 13:59:56 -0400 (EDT)
- Subject: gdb 6.0.92, native hppa2.0w-hp-hpux11.11
The results for gdb 6.0.92 are similar to gdb 6.0.91 with
one significant regression in C++ support.
The inferior-function-call patch did not make a difference
with the compilers that I test with: hp ansi-c and hp aCC.
=== metadata
target = native
host = hppa2.0w-hp-hpux11.11
test-package = gdb 6.0.92
test-suite = gdb 6.0.92
with-package = hpcc B.11.11.28706.GP
with-package = hpacc A.03.45
with-package = hpas UX.11.01.17
with-package = hpld B.11.37
with-package = hplibc 11.11
gformat = default
glevel = default
=== gdb Summary ===
# of ERROR 51
# of WARNING 5
# of expected passes 9066
# of unexpected failures 859
# of unexpected successes 4
# of expected failures 139
# of known failures 28
# of unresolved testcases 49
# of untested testcases 5
# of unsupported tests 16
Here are the differences in results from gdb 6.0.91 to gdb 6.0.92.
-PASS: gdb.base/annota1.exp: Core dumped and removed
+PASS: gdb.base/annota1.exp: No core dumped
Not analyzed.
-FAIL: gdb.base/foll-vfork.exp: running to main in runto
-FAIL: gdb.base/foll-vfork.exp: running to main in runto
-FAIL: gdb.base/foll-vfork.exp: setting breakpoint at main
+ERROR: Delete all breakpoints in delete_breakpoints (timeout)
+UNRESOLVED: gdb.base/foll-vfork.exp: setting breakpoint at main (timeout)
+ERROR: Delete all breakpoints in delete_breakpoints (timeout)
+UNRESOLVED: gdb.base/foll-vfork.exp: setting breakpoint at main (timeout)
+ERROR: Delete all breakpoints in delete_breakpoints (timeout)
+UNRESOLVED: gdb.base/foll-vfork.exp: setting breakpoint at main (timeout)
I get this fluctuation a lot on native hppa2.0w-hp-hpux11.11,
even with back-to-back test runs.
-PASS: gdb.base/pc-fp.exp: get value of $pc (0x2a88)
+PASS: gdb.base/pc-fp.exp: get value of $pc (0x2a90)
Obviously harmless.
-PASS: gdb.cp/classes.exp: ptype class Static
+FAIL: gdb.cp/classes.exp: ptype class Static
gdb regressed from 6.0.91 to 6.0.92.
gdb.log excerpts:
# gdb 6.0.91
ptype class Static
type = class Static {
public:
static void ii(int, int);
}
(gdb) PASS: gdb.cp/classes.exp: ptype class Static
# gdb 6.0.92
ptype class Static
type = class Static {
}
(gdb) FAIL: gdb.cp/classes.exp: ptype class Static
gdb 6.0 does not even build on native hppa2.0w-hp-hpux11.11,
so this is not a regression versus gdb 6.0.
-PASS: gdb.cp/virtfunc.exp: ptype V
+FAIL: gdb.cp/virtfunc.exp: ptype V
This is another case where gdb 6.0.92 omitted a class member.
# gdb 6.0.91
ptype V
type = class V : public VA, public VB {
public:
int w;
int f(void);
virtual int vv(void);
}
(gdb) PASS: gdb.cp/virtfunc.exp: ptype V
# gdb 6.0.92
ptype V
type = class V : public VA, public VB {
public:
int w;
int f(void);
}
(gdb) FAIL: gdb.cp/virtfunc.exp: ptype V
-PASS: gdb.cp/virtfunc.exp: ptype v
+FAIL: gdb.cp/virtfunc.exp: ptype v
More class member omission.
-PASS: gdb.cp/virtfunc.exp: ptype pVa
-PASS: gdb.cp/virtfunc.exp: ptype pVv
-PASS: gdb.cp/virtfunc.exp: ptype pVe
-PASS: gdb.cp/virtfunc.exp: ptype pVd
+FAIL: gdb.cp/virtfunc.exp: ptype pVa
+FAIL: gdb.cp/virtfunc.exp: ptype pVv
+FAIL: gdb.cp/virtfunc.exp: ptype pVe
+FAIL: gdb.cp/virtfunc.exp: ptype pVd
More class member omission.