This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[obv] testsuite: solib-corrupted.exp use specific untested message
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Sat, 18 Aug 2012 09:03:57 +0200
- Subject: [obv] testsuite: solib-corrupted.exp use specific untested message
Hi,
http://sourceware.org/gdb/wiki/GDBTestcaseCookbook
In untested calls, please spell out the reason the test ends up untested,
instead of just writing the test name
Checked in (it was a code by me).
Jan
http://sourceware.org/ml/gdb-cvs/2012-08/msg00140.html
--- src/gdb/testsuite/ChangeLog 2012/08/18 01:00:18 1.3342
+++ src/gdb/testsuite/ChangeLog 2012/08/18 07:02:08 1.3343
@@ -1,3 +1,8 @@
+2012-08-18 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ * gdb.base/solib-corrupted.exp (make solibs looping): Replace
+ verbose -log by more specific untested call.
+
2012-08-18 Yao Qi <yao@codesourcery.com>
* gdb.trace/tfind.exp: Move tests on various command help before
--- src/gdb/testsuite/gdb.base/solib-corrupted.exp 2012/01/04 08:17:46 1.6
+++ src/gdb/testsuite/gdb.base/solib-corrupted.exp 2012/08/18 07:02:09 1.7
@@ -44,9 +44,8 @@
-re "(No symbol \"_r_debug\" in current context\\.|Attempt to extract a component of a value that is not a structure pointer\\.)\r\n$gdb_prompt $" {
# glibc debug info is not available and it is too difficult to find and
# parse it from this testcase without the gdb supporting functions.
- verbose -log "no _r_debug symbol has been found"
xfail $test
- untested ${testfile}.exp
+ untested "no _r_debug symbol has been found"
return
}
-re " = 0x\[0-9a-f\]+\r\n$gdb_prompt $" {