From: Andrew Burgess <aburgess@redhat.com>
Date: Wed, 16 Jul 2025 14:30:48 +0000 (+0100)
Subject: gdb/testsuite: mark the start of each gdb.in.* log file
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f10173a01ffccbad7759ca24336355a87b0948aa;p=thirdparty%2Fbinutils-gdb.git

gdb/testsuite: mark the start of each gdb.in.* log file

Emit a line in the gdb.log file each time a new gdb.in.NUM command log
is started.  The gdb.log line includes the full filename for the new
gdb.in.NUM file.

This change will make it trivial to go from a FAIL in the gdb.log file
to the gdb.in.NUM file that (should) reproduce the failure.  When I
encounter a failing test one of my first steps is usually to identify
the gdb.in.NUM file and try re-running it to see if that reproduces
the failure.  Some tests create many very similar gdb.in.NUM files, so
finding the exact one can sometimes be difficult.  With this patch
that task is now trivial.

There should be no change in what is tested after this commit.

Approved-By: Simon Marchi <simon.marchi@efficios.com>
---

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index f9039dc7bc8..8d94d6b81af 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -9993,6 +9993,10 @@ proc gdb_stdin_log_init { } {
 
     set logfile [standard_output_file_with_gdb_instance gdb.in]
     set in_file [open $logfile w]
+
+    verbose -log ""
+    verbose -log "Starting logfile: $logfile"
+    verbose -log ""
 }
 
 # Write to the file for logging gdb input.