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-12-branch] [gdb/testsuite] Fix gdb.base/stap-probe.exp with read1
Date: Thu, 14 Apr 2022 11:52:23 +0000 (GMT)	[thread overview]
Message-ID: <20220414115223.86B093858C53@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f48fc32448205963c597975f1bce3db3c86094ad

commit f48fc32448205963c597975f1bce3db3c86094ad
Author: Tom de Vries <tdevries@suse.de>
Date:   Thu Apr 14 13:52:19 2022 +0200

    [gdb/testsuite] Fix gdb.base/stap-probe.exp with read1
    
    When running test-case gdb.base/stap-probe.exp with make target check-read1, I
    run into this and similar:
    ...
    FAIL: gdb.base/stap-probe.exp: without semaphore, not optimized: \
      info probes stap (timeout)
    ...
    
    Fix this by using gdb_test_lines instead of gdb_test.
    
    Tested on x86_64-linux.

Diff:
---
 gdb/testsuite/gdb.base/stap-probe.exp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.base/stap-probe.exp b/gdb/testsuite/gdb.base/stap-probe.exp
index e86c7897b93..75ad56baff6 100644
--- a/gdb/testsuite/gdb.base/stap-probe.exp
+++ b/gdb/testsuite/gdb.base/stap-probe.exp
@@ -42,10 +42,10 @@ proc stap_test {exec_name {args ""}} {
 	"check argument not at probe point"
 
     if {[string first "-DUSE_SEMAPHORES" $args] != -1} {
-	gdb_test "info probes stap" \
+	gdb_test_lines "info probes stap" "" \
 	    "test *user *$hex *$hex .*"
     } else {
-	gdb_test "info probes stap" \
+	gdb_test_lines "info probes stap" "" \
 	    "test *user *$hex .*"
     }


                 reply	other threads:[~2022-04-14 11:52 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=20220414115223.86B093858C53@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: link
Be 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).