aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2023-04-22 11:04:11 +0200
committerTom de Vries <tdevries@suse.de>2023-04-22 11:04:11 +0200
commitf41c2f5edda3e009566c96cf4ae27908d0387d36 (patch)
tree92f15111c2644abae3e8c78e9dd9561d6c11eebc
parenta88ee931eee4ba7339c481735b9405f66161e2f6 (diff)
downloadgdb-f41c2f5edda3e009566c96cf4ae27908d0387d36.zip
gdb-f41c2f5edda3e009566c96cf4ae27908d0387d36.tar.gz
gdb-f41c2f5edda3e009566c96cf4ae27908d0387d36.tar.bz2
[gdb/testsuite] Remove debug prints in gdb_find_gdc
When running the gdb.dlang test-cases, and forcing gdb_find_gdc to be used rather than dejagnu's copy (mimicing what happens with an older dejagnu without find_gdc), I run into these debug prints: ... Tool Root: /data/vries/gdb/leap-15-4/build CC: gdc ... Remove these. Tested on x86_64-linux.
-rw-r--r--gdb/testsuite/lib/future.exp3
1 files changed, 1 insertions, 2 deletions
diff --git a/gdb/testsuite/lib/future.exp b/gdb/testsuite/lib/future.exp
index fa839fc..807053b 100644
--- a/gdb/testsuite/lib/future.exp
+++ b/gdb/testsuite/lib/future.exp
@@ -43,7 +43,6 @@ proc gdb_find_gnatmake {} {
proc gdb_find_gdc {} {
global tool_root_dir
- print "Tool Root: $tool_root_dir"
if {![is_remote host]} {
set file [lookfor_file $tool_root_dir gdc]
@@ -58,7 +57,7 @@ proc gdb_find_gdc {} {
} else {
set CC [transform gdc]
}
- print "CC: $CC"
+
return $CC
}