From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] testsuite/gdb.c++/derivation.exp: use 'runto' library function
Date: Mon, 12 Mar 2001 02:05:00 -0000 [thread overview]
Message-ID: <200103121005.CAA00765@bosch.cygnus.com> (raw)
This is Sunday Project Patch #7.
This patch changes gdb.c++/derivation.exp to use the library function
'runto' to reach a marker function. This simplifies the file. The real
benefit is that 'runto' accommodates an unrelated bug in gdb (PR gdb/34,
"g++ v3 functions show as "inheritance2() ()""). This enables the
keep its synchronization and do its job testing C++.
Before this patch, this test script outputs 20 FAILs + 3 XFAILs.
After this patch, output is 16 PASSes + 4 FAILs + 3 XPASSes.
I tested this on Red Hat Linux 7 native and Solaris 2.5.1 native with
gcc 2.95.2 and gcc 3pre dated 2001-03-09.
OK to apply?
Michael
===
2001-03-12 Michael Chastain <chastain@redhat.com>
* gdb.c++/derivation.exp: Use the 'runto' library function.
===
Index: gdb/testsuite/gdb.c++/derivation.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.c++/derivation.exp,v
retrieving revision 1.4
diff -c -3 -p -r1.4 derivation.exp
*** gdb/testsuite/gdb.c++/derivation.exp 2001/03/06 08:21:52 1.4
--- gdb/testsuite/gdb.c++/derivation.exp 2001/03/12 09:34:43
***************
*** 1,4 ****
! # Copyright 1998, 1999, 2000 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
--- 1,4 ----
! # Copyright 1998, 1999, 2000, 2001 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
*************** if ![runto_main] then {
*** 69,93 ****
continue
}
! send_gdb "break marker1\n" ; gdb_expect -re ".*$gdb_prompt $"
! send_gdb "cont\n"
! gdb_expect {
! -re "Break.* marker1 \\(\\) at .*:$decimal.*$gdb_prompt $" {
! send_gdb "up\n"
! gdb_expect {
! -re ".*main.*$gdb_prompt $" {
! pass "up from marker1"
! }
! -re ".*$gdb_prompt $" {
! fail "up from marker1"
! }
! timeout { fail "up from marker1 (timeout)" }
! }
! }
! -re "$gdb_prompt $" { fail "continue to marker1" }
! timeout { fail "(timeout) continue to marker1" }
! }
--- 69,80 ----
continue
}
! if ![runto 'marker1'] then {
! perror "couldn't run to marker1"
! continue
! }
! gdb_test "up" ".*main.*" "up from marker1"
next reply other threads:[~2001-03-12 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 2:05 Michael Elizabeth Chastain [this message]
2001-03-12 11:52 ` Michael Snyder
2001-03-12 12:17 Michael Elizabeth Chastain
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=200103121005.CAA00765@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/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