This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch/rfc] Check for CFI complaints


Hello,

This patch modifies savedregs.exp (it should probably be called infoframe) so that it checks for, and fails on, messages such as:

During symbol reading, incomplete CFI data; unspecified registers (e.g., r0) at 0x10000548.

thoughts?
Andrew
2004-11-05  Andrew Cagney  <cagney@gnu.org>

	* gdb.base/savedregs.exp (process_saved_regs): Enable complaints.
	Fail when there's symbol complaint.

Index: testsuite/gdb.base/savedregs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/savedregs.exp,v
retrieving revision 1.1
diff -p -u -r1.1 savedregs.exp
--- testsuite/gdb.base/savedregs.exp	3 Nov 2004 14:46:18 -0000	1.1
+++ testsuite/gdb.base/savedregs.exp	6 Nov 2004 01:03:14 -0000
@@ -94,6 +94,10 @@ proc process_saved_regs { current inner 
 	# If the "info frame" barf, capture the output anyway so that
 	# it does not cascade further failures.
 	gdb_test_multiple "info frame $level" "$test" {
+	    -re "(During symbol reading.*)$gdb_prompt " {
+		set saved_regs($func) "$expect_out(1,string)"
+		fail "$test (symbol complaint)"
+	    }
 	    -re "($pat)$gdb_prompt " {
 		set saved_regs($func) "$expect_out(1,string)"
 		pass "$test"
@@ -139,6 +143,8 @@ proc process_saved_regs { current inner 
 }
 
 
+gdb_test "set complaints 1"
+
 # Continue to the signal thrower, capture main's saved-reg info.
 gdb_test "advance thrower" "thrower .* at .*"
 process_saved_regs thrower { main } { }

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]