Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [RFA] gdb.python, gdb.reverse, gdb.server, use gdb_test_no_output
Date: Wed, 02 Jun 2010 20:18:00 -0000	[thread overview]
Message-ID: <4C06BC77.9040300@vmware.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2: python.exp.txt --]
[-- Type: text/plain, Size: 6856 bytes --]

2010-06-02  Michael Snyder  <msnyder@vmware.com>

	* gdb.python/py-block.exp: Use gdb_test_no_output.
	* gdb.python/py-prettyprint.exp: Ditto.
	* gdb.python/py-template.exp: Ditto.
	* gdb.python/py-value.exp: Ditto.

	* gdb.reverse/watch-precsave.exp: Use gdb_test_no_output.
	* gdb.reverse/watch-reverse.exp: Ditto.

	* gdb.server/ext-attach.exp: Use gdb_test_no_output.
	* gdb.server/ext-run.exp: Ditto.

Index: gdb.python/py-block.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.python/py-block.exp,v
retrieving revision 1.1
diff -u -p -r1.1 py-block.exp
--- gdb.python/py-block.exp	24 Feb 2010 21:18:28 -0000	1.1
+++ gdb.python/py-block.exp	2 Jun 2010 20:11:47 -0000
@@ -66,9 +66,9 @@ gdb_test "python print block.start" "${d
 gdb_test "python print block.end" "${decimal}" "Check end not None"
 
 # Move up superblock(s) until we reach function block_func.
-gdb_test "python block = block.superblock" "" "Get superblock"
+gdb_test_no_output "python block = block.superblock" "Get superblock"
 gdb_test "python print block.function" "None" "Second anonymous block"
-gdb_test "python block = block.superblock" "" "Get superblock"
+gdb_test_no_output "python block = block.superblock" "Get superblock 2"
 gdb_test "python print block.function" "block_func"
 
 # Switch frames, then test for main block.
Index: gdb.python/py-prettyprint.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.python/py-prettyprint.exp,v
retrieving revision 1.8
diff -u -p -r1.8 py-prettyprint.exp
--- gdb.python/py-prettyprint.exp	14 Apr 2010 12:02:46 -0000	1.8
+++ gdb.python/py-prettyprint.exp	2 Jun 2010 20:11:47 -0000
@@ -63,7 +63,7 @@ proc run_lang_tests {lang} {
 	return
     }
 
-    gdb_test "set print pretty on" ""
+    gdb_test_no_output "set print pretty on"
 
     gdb_test "b [gdb_get_line_number {break to inspect} ${testfile}.c ]" \
 	".*Breakpoint.*"
@@ -71,7 +71,7 @@ proc run_lang_tests {lang} {
 
     set remote_python_file [remote_download host ${srcdir}/${subdir}/${testfile}.py]
 
-    gdb_test "python execfile ('${remote_python_file}')" ""
+    gdb_test_no_output "python execfile ('${remote_python_file}')"
     
     gdb_test "print ss" " = a=< a=<1> b=<$hex>> b=< a=<2> b=<$hex>>"
     gdb_test "print ssa\[1\]" " = a=< a=<5> b=<$hex>> b=< a=<6> b=<$hex>>"
Index: gdb.python/py-template.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.python/py-template.exp,v
retrieving revision 1.3
diff -u -p -r1.3 py-template.exp
--- gdb.python/py-template.exp	24 Feb 2010 11:11:16 -0000	1.3
+++ gdb.python/py-template.exp	2 Jun 2010 20:11:47 -0000
@@ -53,7 +53,7 @@ proc test_template_arg {type} {
     }
     # There is no executable code in main(), so we are where we want to be
     gdb_test "print foo" ""
-    gdb_test "python foo = gdb.history(0)" ""
+    gdb_test_no_output "python foo = gdb.history(0)"
 
     # Replace '*' with '\*' in regex.
     regsub -all {\*} $type {\*} t
Index: gdb.python/py-value.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.python/py-value.exp,v
retrieving revision 1.9
diff -u -p -r1.9 py-value.exp
--- gdb.python/py-value.exp	14 May 2010 11:11:28 -0000	1.9
+++ gdb.python/py-value.exp	2 Jun 2010 20:11:47 -0000
@@ -116,7 +116,7 @@ proc test_value_numeric_ops {} {
 
   # Conversion test.
   gdb_test "print evalue" " = TWO"
-  gdb_test "python evalue = gdb.history (0)" ""
+  gdb_test_no_output "python evalue = gdb.history (0)"
   gdb_test "python print int (evalue)" "2"
 
   # Test pointer arithmethic
Index: gdb.reverse/watch-precsave.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.reverse/watch-precsave.exp,v
retrieving revision 1.4
diff -u -p -r1.4 watch-precsave.exp
--- gdb.reverse/watch-precsave.exp	28 May 2010 18:26:41 -0000	1.4
+++ gdb.reverse/watch-precsave.exp	2 Jun 2010 20:11:47 -0000
@@ -139,7 +139,7 @@ gdb_test "continue" \
     ".*\[Ww\]atchpoint.*ival3.*Old value = 0.*New value = -1.*ival3 = count; ival4 = count;.*" \
     "watchpoint hit in reverse, fifth time"
 
-gdb_test "set can-use-hw-watchpoints 1" "" "enable hw watchpoints"
+gdb_test_no_output "set can-use-hw-watchpoints 1" "enable hw watchpoints"
 
 ###
 ###
Index: gdb.reverse/watch-reverse.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.reverse/watch-reverse.exp,v
retrieving revision 1.5
diff -u -p -r1.5 watch-reverse.exp
--- gdb.reverse/watch-reverse.exp	28 May 2010 18:26:41 -0000	1.5
+++ gdb.reverse/watch-reverse.exp	2 Jun 2010 20:11:47 -0000
@@ -38,7 +38,7 @@ if [target_info exists gdb,use_precord] 
 }
 
 # Test software watchpoints
-gdb_test "set can-use-hw-watchpoints 0" "" "disable hw watchpoints"
+gdb_test_no_output "set can-use-hw-watchpoints 0" "disable hw watchpoints"
 
 gdb_test "break marker1" \
     "Breakpoint $decimal at $hex: file .*$srcfile, line $decimal.*" \
@@ -121,7 +121,7 @@ gdb_test "continue" \
     ".*\[Ww\]atchpoint.*ival3.*Old value = 0.*New value = -1.*ival3 = count; ival4 = count;.*" \
     "watchpoint hit in reverse, fifth time"
 
-gdb_test "set can-use-hw-watchpoints 1" "" "enable hw watchpoints"
+gdb_test_no_output "set can-use-hw-watchpoints 1" "enable hw watchpoints"
 
 ###
 ###
Index: gdb.server/ext-attach.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.server/ext-attach.exp,v
retrieving revision 1.6
diff -u -p -r1.6 ext-attach.exp
--- gdb.server/ext-attach.exp	12 Jan 2010 00:50:26 -0000	1.6
+++ gdb.server/ext-attach.exp	2 Jun 2010 20:11:47 -0000
@@ -45,7 +45,7 @@ gdb_reinitialize_dir $srcdir/$subdir
 set target_exec [gdbserver_download_current_prog]
 gdbserver_start_extended
 
-gdb_test "set remote exec-file $target_exec" "" "set remote exec-file"
+gdb_test_no_output "set remote exec-file $target_exec" "set remote exec-file"
 
 # Start the program running and then wait for a bit, to be sure
 # that it can be attached to.
Index: gdb.server/ext-run.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.server/ext-run.exp,v
retrieving revision 1.8
diff -u -p -r1.8 ext-run.exp
--- gdb.server/ext-run.exp	12 Jan 2010 00:50:26 -0000	1.8
+++ gdb.server/ext-run.exp	2 Jun 2010 20:11:47 -0000
@@ -43,7 +43,7 @@ gdb_reinitialize_dir $srcdir/$subdir
 set target_exec [gdbserver_download_current_prog]
 gdbserver_start_extended
 
-gdb_test "set remote exec-file $target_exec" "" "set remote exec-file"
+gdb_test_no_output "set remote exec-file $target_exec" "set remote exec-file"
 
 gdb_breakpoint main
 gdb_test "run" "Breakpoint.* main .*" "continue to main"

             reply	other threads:[~2010-06-02 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02 20:18 Michael Snyder [this message]
2010-06-02 21:35 ` Joel Brobecker
2010-06-02 21:51   ` Michael Snyder

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=4C06BC77.9040300@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    /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