From 29f25f6f6974faf467f8545941cf4d4b8dfe0188 Mon Sep 17 00:00:00 2001
From: Jim Kingdon <jkingdon@engr.sgi.com>
Date: Tue, 17 Jan 1995 16:22:23 +0000
Subject: [PATCH] 	* gdb.base/nodebug.exp: Add tests to check that
 "print", "whatis" 	and "ptype" work on variables in files compiled
 without -g. 	Replaces commented out "maint print msymbol" tests.

---
 gdb/testsuite/ChangeLog            |  6 +++
 gdb/testsuite/gdb.base/nodebug.exp | 70 ++++++++++++++++++++++++++++++
 2 files changed, 76 insertions(+)
 create mode 100644 gdb/testsuite/gdb.base/nodebug.exp

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 742330377a6..91c36d3ad38 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+Tue Jan 17 10:47:53 1995  Jim Kingdon  <kingdon@lioth.cygnus.com>
+
+	* gdb.base/nodebug.exp: Add tests to check that "print", "whatis"
+	and "ptype" work on variables in files compiled without -g.
+	Replaces commented out "maint print msymbol" tests.
+
 Mon Jan 16 12:13:28 1995  Jim Kingdon  <kingdon@lioth.cygnus.com>
 
 	* gdb.base/setvar.c (dummy): Call malloc.
diff --git a/gdb/testsuite/gdb.base/nodebug.exp b/gdb/testsuite/gdb.base/nodebug.exp
new file mode 100644
index 00000000000..52f6bd1a8a4
--- /dev/null
+++ b/gdb/testsuite/gdb.base/nodebug.exp
@@ -0,0 +1,70 @@
+# Test that things still (sort of) work when compiled without -g.
+# In gdb.t10 because it is related to symbol-reading, and so are the crossload
+# tests.
+
+if $tracelevel then {
+	strace $tracelevel
+}
+
+set prms_id 0
+set bug_id 0
+
+set binfile $objdir/$subdir/nodebug
+
+if ![file exists $binfile] then {
+    perror "$binfile does not exist."
+    return 0
+} else {
+    gdb_reinitialize_dir $srcdir/$subdir
+    gdb_load $binfile
+
+    if [runto inner] then {
+
+	# Expect to find global/local symbols in each of text/data/bss.
+
+	# The exact format for some of this output is not necessarily
+	# ideal, particularly interpreting "p top" requires a fair bit of
+	# savvy about gdb's workings and the meaning of the "{}"
+	# construct.  So the details maybe could be tweaked.  But the
+	# basic purpose should be maintained, which is (a) users should be
+	# able to interact with these variables with some care (they have
+	# to know how to interpret them according to their real type,
+	# since gdb doesn't know the type), but (b) users should be able
+	# to detect that gdb does not know the type, rather than just
+	# being told they are ints or functions returning int like old
+	# versions of gdb used to do.
+
+	gdb_test "p top" "{<text variable without -g>} \[0-9a-fx]* <top>"
+	gdb_test "whatis top" "<text variable without -g>"
+	gdb_test "ptype top" "int \\(\\)"
+
+	gdb_test "p middle" "{<text variable without -g>} \[0-9a-fx]* <middle>"
+	gdb_test "whatis middle" "<text variable without -g>"
+	gdb_test "ptype middle" "int \\(\\)"
+
+	gdb_test "p dataglobal" "= 3"
+	gdb_test "whatis dataglobal" "<data variable without -g>"
+	gdb_test "ptype dataglobal" "<data variable without -g>"
+
+	gdb_test "p datalocal" "= 4"
+	gdb_test "whatis datalocal" "<data variable without -g>"
+	gdb_test "ptype datalocal" "<data variable without -g>"
+
+	gdb_test "p bssglobal" "= 0"
+	gdb_test "whatis bssglobal" "<data variable without -g>"
+	gdb_test "ptype bssglobal" "<data variable without -g>"
+
+	gdb_test "p bsslocal" "= 0"
+	gdb_test "whatis bsslocal" "<data variable without -g>"
+	gdb_test "ptype bsslocal" "<data variable without -g>"
+
+	gdb_test "backtrace" "#0.*inner.*#1.*middle.*#2.*top.*#3.*main"
+	# Or if that doesn't work, at least hope for the external symbols
+	gdb_test "backtrace" "#0.*inner.*#1.*#2.*top.*#3.*main"
+	# Now, try that we can give names of file-local symbols which happen
+	# to be unique, and have it still work
+	if [runto middle] then {
+	    gdb_test "backtrace" "#0.*middle.*#1.*top.*#2.*main"
+	}
+    }
+}
-- 
2.30.2