public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Remove debug prints in gdb_find_gdc
Date: Sat, 22 Apr 2023 11:05:09 +0200	[thread overview]
Message-ID: <20230422090509.17831-1-tdevries@suse.de> (raw)

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.
---
 gdb/testsuite/lib/future.exp | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/gdb/testsuite/lib/future.exp b/gdb/testsuite/lib/future.exp
index fa839fcd12b..807053b8f94 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
 }
 

base-commit: a88ee931eee4ba7339c481735b9405f66161e2f6
-- 
2.35.3


                 reply	other threads:[~2023-04-22  9:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230422090509.17831-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).