From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: give store.exp tests unique names
Date: Thu, 06 Nov 2003 04:57:00 -0000 [thread overview]
Message-ID: <vt24qxirt6t.fsf@zenia.home> (raw)
Doesn't Michael C.'s system detect duplicate test names? Perhaps I am
doing something wrong.
2003-11-05 Jim Blandy <jimb@redhat.com>
* gdb.base/store.exp: Make sure every test has a unique name.
Index: gdb/testsuite/gdb.base/store.exp
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/store.exp,v
retrieving revision 1.4
diff -c -r1.4 store.exp
*** gdb/testsuite/gdb.base/store.exp 14 Aug 2003 22:44:06 -0000 1.4
--- gdb/testsuite/gdb.base/store.exp 6 Nov 2003 04:47:03 -0000
***************
*** 61,69 ****
gdb_test "next" "l = add_${t} .l, r.;" "next ${t}"
gdb_test "print l" " = ${l}" "print old l - ${t}"
gdb_test "print r" " = ${r}" "print old r - ${t}"
! gdb_test "set variable l = 4"
gdb_test "print l" " = ${new}" "print new l - ${t}"
! gdb_test "next" "return l \\+ r;"
gdb_test "print l" " = ${add}" "print add - ${t}"
}
--- 61,69 ----
gdb_test "next" "l = add_${t} .l, r.;" "next ${t}"
gdb_test "print l" " = ${l}" "print old l - ${t}"
gdb_test "print r" " = ${r}" "print old r - ${t}"
! gdb_test "set variable l = 4" "" "set l - ${t}"
gdb_test "print l" " = ${new}" "print new l - ${t}"
! gdb_test "next" "return l \\+ r;" "next over call - ${t}"
gdb_test "print l" " = ${add}" "print add - ${t}"
}
***************
*** 85,91 ****
gdb_test "up" "l = add_${t} .l, r.;" "up ${t}"
gdb_test "print l" " = ${l}" "up print old l - ${t}"
gdb_test "print r" " = ${r}" "up print old r - ${t}"
! gdb_test "set variable l = 4"
gdb_test "print l" " = ${new}" "up print new l - ${t}"
}
--- 85,91 ----
gdb_test "up" "l = add_${t} .l, r.;" "up ${t}"
gdb_test "print l" " = ${l}" "up print old l - ${t}"
gdb_test "print r" " = ${r}" "up print old r - ${t}"
! gdb_test "set variable l = 4" "" "up set l - ${t}"
gdb_test "print l" " = ${new}" "up print new l - ${t}"
}
***************
*** 105,113 ****
gdb_test "tbreak wack_struct_${t}"
gdb_test "continue" "int i; register struct s_${t} u = z_${t};" \
"continue set struct ${t}"
! gdb_test "next 2" "add_struct_${t} .u.;"
gdb_test "print u" " = ${old}" "old check struct ${t}"
! gdb_test "set variable u = s_${t}"
gdb_test "print u" " = ${new}" "new check struct ${t}"
}
--- 105,113 ----
gdb_test "tbreak wack_struct_${t}"
gdb_test "continue" "int i; register struct s_${t} u = z_${t};" \
"continue set struct ${t}"
! gdb_test "next 2" "add_struct_${t} .u.;" "check struct next ${t}"
gdb_test "print u" " = ${old}" "old check struct ${t}"
! gdb_test "set variable u = s_${t}" "" "set check struct ${t}"
gdb_test "print u" " = ${new}" "new check struct ${t}"
}
***************
*** 123,129 ****
"continue up struct ${t}"
gdb_test "up" "u = add_struct_${t} .u.;" "up struct ${t}"
gdb_test "print u" " = ${old}" "old up struct ${t}"
! gdb_test "set variable u = s_${t}"
gdb_test "print u" " = ${new}" "new up struct ${t}"
}
--- 123,129 ----
"continue up struct ${t}"
gdb_test "up" "u = add_struct_${t} .u.;" "up struct ${t}"
gdb_test "print u" " = ${old}" "old up struct ${t}"
! gdb_test "set variable u = s_${t}" "" "set up struct ${t}"
gdb_test "print u" " = ${new}" "new up struct ${t}"
}
next reply other threads:[~2003-11-06 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 4:57 Jim Blandy [this message]
2003-11-06 6:44 Michael Elizabeth Chastain
2003-11-06 7:38 ` Jim Blandy
2003-11-06 16:49 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=vt24qxirt6t.fsf@zenia.home \
--to=jimb@redhat.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