Keith Seitz c1854f1d5a Use gdb_test_no_output for compile tests expected to pass ... There is a small think-o in compile.exp: if { $srcfile3 != "" } { gdb_test "p constvar" " = 3" gdb_test "info addr constvar" {Symbol "constvar" is constant\.} gdb_test "compile code globalvar = constvar;"; # INCORRECT gdb_test "print globalvar" " = 3" "print constvar value" } else { untested "print constvar value" } The line marked INCORRECT runs a simple "compile code" which is expected to succeed. When this happens, the compile plug-in and GDB will not output anything. The use of gdb_test matches against anything. This is certainly not the intent, and this patch corrects the two instances of this in the file. [The rest of gdb.compile looks okay.] testsuite/ChangeLog: * gdb.compile/compile.exp: Use gdb_test_no_output for "compile code" tests expected to pass.		2018-08-16 17:00:16 -07:00
..
compile-constvar.c
compile-constvar.S
compile-ifunc.c
compile-ifunc.exp
compile-mod.c
compile-nodebug.c
compile-ops.c
compile-ops.exp
compile-print.c
compile-print.exp
compile-setjmp-mod.c
compile-setjmp.c
compile-setjmp.exp
compile-shlib.c
compile-tls.c
compile-tls.exp
compile.c
compile.exp