This is the mail archive of the 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, testsuite] check for UTF-32 target wide charset support in gdb.base/wchar.exp

This patch is related to the one I posted yesterday to make with_target_charset do something reasonable in the absence of ICONV support:

If GDB is configured without ICONV support, the target wide charset defaults to "ISO-8859-1" (which isn't even a wide charset), and all the wide strings in this test print as gibberish. Otherwise, GDB seems to think the default is "auto; currently UTF-32", so let's make the dependency on UTF-32 explicit here and bail out if it's not available.

OK to commit?


2015-09-16  Sandra Loosemore  <>

	* gdb.base/wchar.exp: Require UTF-32 target wide charset support,
	otherwise skip this test.
diff --git a/gdb/testsuite/gdb.base/wchar.exp b/gdb/testsuite/gdb.base/wchar.exp
index 1a5a2d4..171385b 100644
--- a/gdb/testsuite/gdb.base/wchar.exp
+++ b/gdb/testsuite/gdb.base/wchar.exp
@@ -24,6 +24,19 @@ if ![runto "wchar.c:$bp_location" ] then {
   return -1
+# This test requires wide character support in GDB.
+# Setting the charset may fail if GDB was configured without
+# ICONV support.
+gdb_test_multiple "set target-wide-charset UTF-32" "" {
+    -re "Undefined item.*$gdb_prompt " {
+	unsupported "Unknown charset UTF-32"
+	return -1
+    }
+    -re ".*$gdb_prompt " {
+	pass "set target-wide-charset UTF-32"
+    }
 gdb_test "print narrow" "= 97 L'a'"
 gdb_test "print single" "= 48879 L'\\\\xbeef'"

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