public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: handle long filenames in gdb.base/startup-with-shell.exp Date: Wed, 17 Jan 2024 15:38:58 +0000 (GMT) [thread overview] Message-ID: <20240117153858.6D3B63858CDB@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=52498004a34dfa4bc55fbf791a4ed4e81599a436 commit 52498004a34dfa4bc55fbf791a4ed4e81599a436 Author: Andrew Burgess <aburgess@redhat.com> Date: Wed Jan 17 09:53:16 2024 +0000 gdb/testsuite: handle long filenames in gdb.base/startup-with-shell.exp I got a report of a failure from Linaro's CI testing for the test gdb.base/startup-with-shell.exp. Looking at the log I see this: (gdb) PASS: gdb.base/startup-with-shell.exp: startup_with_shell = on; run_args = *.unique-extension: inferior started print argv[1] $1 = 0xfffed978 "/home/tcwg-build/workspace/tcwg_gnu_4/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/gdb-gdb.git~master/gdb/testsuite/outputs/gdb.base/startup-with-shell/unique-file.unique-e"... (gdb) FAIL: gdb.base/startup-with-shell.exp: startup_with_shell = on; run_args = *.unique-extension: first argument expanded Notice that the value of $1 was truncated (indicated by the trailing ellipses), and as a result it isn't going to match the expected output pattern. Avoid this by adding a call to 'set print characters unlimited' which allows GDB to print strings of any length. Approved-By: Tom de Vries <tdevries@suse.de> Diff: --- gdb/testsuite/gdb.base/startup-with-shell.exp | 1 + 1 file changed, 1 insertion(+) diff --git a/gdb/testsuite/gdb.base/startup-with-shell.exp b/gdb/testsuite/gdb.base/startup-with-shell.exp index b73d5d740f5..d5ec503dceb 100644 --- a/gdb/testsuite/gdb.base/startup-with-shell.exp +++ b/gdb/testsuite/gdb.base/startup-with-shell.exp @@ -59,6 +59,7 @@ proc initial_setup_simple { startup_with_shell run_args } { with_test_prefix "startup_with_shell = on; run_args = *.unique-extension" { initial_setup_simple "on" "$unique_file_dir/*.unique-extension" + gdb_test_no_output "set print characters unlimited" gdb_test "print argv\[1\]" "\\\$$decimal = $hex \"$unique_file\"" \ "first argument expanded" }
reply other threads:[~2024-01-17 15:38 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=20240117153858.6D3B63858CDB@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).