public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix regexp in gdb.threads/dlopen-libpthread.exp Date: Wed, 11 Jan 2023 17:37:24 +0000 (GMT) [thread overview] Message-ID: <20230111173724.A55B63858C83@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1b9af5b949bff0c750ededb459400c1857fec416 commit 1b9af5b949bff0c750ededb459400c1857fec416 Author: Simon Marchi <simon.marchi@polymtl.ca> Date: Wed Jan 11 18:37:20 2023 +0100 [gdb/testsuite] Fix regexp in gdb.threads/dlopen-libpthread.exp Fix regexp in gdb.threads/dlopen-libpthread.exp: 'libpthread\\.so' -> '/libpthread\\.so'. Tested on x86_64-linux. Diff: --- gdb/testsuite/gdb.threads/dlopen-libpthread.exp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gdb/testsuite/gdb.threads/dlopen-libpthread.exp b/gdb/testsuite/gdb.threads/dlopen-libpthread.exp index 134265ff470..c97e0284475 100644 --- a/gdb/testsuite/gdb.threads/dlopen-libpthread.exp +++ b/gdb/testsuite/gdb.threads/dlopen-libpthread.exp @@ -68,14 +68,14 @@ if { !$have_probe } { # due to LD_PRELOAD. set libpthread_maybe_preloaded 0 set binfile [standard_output_file $executable] -if { [has_dependency $binfile libpthread\\.so] == 1 } { +if { [has_dependency $binfile /libpthread\\.so] == 1 } { set libpthread_maybe_preloaded 1 } # We link the shlib with -lpthread, but since glibc 2.34 libpthread has been # merged with libc, so libpthread.so may not be a dependency. set libpthread_missing 0 -if { [has_dependency $binfile_lib libpthread\\.so] == 0 } { +if { [has_dependency $binfile_lib /libpthread\\.so] == 0 } { set libpthread_missing 1 }
reply other threads:[~2023-01-11 17:37 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=20230111173724.A55B63858C83@sourceware.org \ --to=vries@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).