public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Use require is_elf_target Date: Fri, 13 Jan 2023 20:36:13 +0000 (GMT) [thread overview] Message-ID: <20230113203613.3085C3858C39@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=28343f921b49dc01414615e5e8a2803ed5fb57cf commit 28343f921b49dc01414615e5e8a2803ed5fb57cf Author: Tom Tromey <tom@tromey.com> Date: Wed Dec 14 09:50:51 2022 -0700 Use require is_elf_target This changes some tests to use "require is_elf_target". Diff: --- gdb/testsuite/gdb.base/rtld-step.exp | 4 +--- gdb/testsuite/gdb.base/sym-file.exp | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/gdb/testsuite/gdb.base/rtld-step.exp b/gdb/testsuite/gdb.base/rtld-step.exp index 473c6c9f7d5..99f1a822b8d 100644 --- a/gdb/testsuite/gdb.base/rtld-step.exp +++ b/gdb/testsuite/gdb.base/rtld-step.exp @@ -35,9 +35,7 @@ # or for non-ELF targets. (We're not really testing or building # shared libraries here, but having a RTLD implies having shared # libraries on the target.) -if { [skip_shlib_tests] || ![is_elf_target] } { - return 0 -} +require !skip_shlib_tests is_elf_target # (Pretend) RTLD file names and flags: set rtld_basename ${::gdb_test_file_name}-rtld diff --git a/gdb/testsuite/gdb.base/sym-file.exp b/gdb/testsuite/gdb.base/sym-file.exp index 666bf96d38e..c4c5f746943 100644 --- a/gdb/testsuite/gdb.base/sym-file.exp +++ b/gdb/testsuite/gdb.base/sym-file.exp @@ -29,9 +29,7 @@ # 13) Check that the execution can continue without error. # 14) Regression test for a stale breakpoints bug. -if {![is_elf_target]} { - return 0 -} +require is_elf_target require !skip_shlib_tests
reply other threads:[~2023-01-13 20:36 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=20230113203613.3085C3858C39@sourceware.org \ --to=tromey@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).