From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] gdb.base/callfuncs.exp: make all test names unique
Date: Sun, 20 May 2001 05:03:00 -0000 [thread overview]
Message-ID: <200105201208.FAA10061@bosch.cygnus.com> (raw)
This patch changes gdb.base/callfuncs.exp to make all test names unique.
Testing: I tested this on native Red Hat Linux 7 and native Solaris 2.8.
OK to apply?
Michael
===
2001-05-19 Michael Chastain <chastain@redhat.com>
* gdb.base/callfuncs.exp: Make all test names unique.
Index: gdb/testsuite/gdb.base/callfuncs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/callfuncs.exp,v
retrieving revision 1.4
diff -c -3 -p -r1.4 callfuncs.exp
*** gdb/testsuite/gdb.base/callfuncs.exp 2001/03/06 08:21:50 1.4
--- gdb/testsuite/gdb.base/callfuncs.exp 2001/05/20 05:39:03
*************** if { $hp_aCC_compiler } {
*** 292,299 ****
# Make sure that malloc gets called and that the floating point unit
# is initialized via a call to t_double_values.
! gdb_test "next" "t_double_values\\(double_val1, double_val2\\);.*"
! gdb_test "next" "t_structs_c\\(struct_val1\\);.*"
# Save all register contents.
do_get_all_registers
--- 292,299 ----
# Make sure that malloc gets called and that the floating point unit
# is initialized via a call to t_double_values.
! gdb_test "next" "t_double_values\\(double_val1, double_val2\\);.*" "next 1"
! gdb_test "next" "t_structs_c\\(struct_val1\\);.*" "next 2"
# Save all register contents.
do_get_all_registers
next reply other threads:[~2001-05-20 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 5:03 Michael Elizabeth Chastain [this message]
2001-05-21 10:52 ` Michael Snyder
2001-05-23 9:40 ` Fernando Nasser
2001-05-21 11:12 Michael Elizabeth Chastain
[not found] <200105231816.LAA13966@bosch.cygnus.com>
2001-05-23 11:20 ` Fernando Nasser
2001-05-23 12:15 Michael Elizabeth Chastain
2001-05-23 15:19 ` Fernando Nasser
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=200105201208.FAA10061@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