aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/python.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2025-07-16 15:30:48 +0100
committerAndrew Burgess <aburgess@redhat.com>2025-07-18 11:25:38 +0100
commitf10173a01ffccbad7759ca24336355a87b0948aa (patch)
tree5e97564ba98bb9742da1251204f49221a49cbca9 /gdb/python/python.c
parentcd47b8fa56726c0f544f03588cbfaf32307215cd (diff)
downloadbinutils-f10173a01ffccbad7759ca24336355a87b0948aa.zip
binutils-f10173a01ffccbad7759ca24336355a87b0948aa.tar.gz
binutils-f10173a01ffccbad7759ca24336355a87b0948aa.tar.bz2
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>
Diffstat (limited to 'gdb/python/python.c')
0 files changed, 0 insertions, 0 deletions