From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/2] gdb: testsuite: remove pass statement in can_spawn_for_attach
Date: Fri, 4 Mar 2022 18:15:26 +0800 [thread overview]
Message-ID: <1646388927-28165-1-git-send-email-yangtiezhu@loongson.cn> (raw)
After execute the following command:
make check-gdb TESTS="gdb.base/attach-pie-noexec.exp"
we can see the following messages in gdb/testsuite/gdb.log:
(gdb) gdb_do_cache_wrap ignoring pass: can spawn for attach
the pass statement is ignored, just remove them in can_spawn_for_attach.
Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
---
gdb/testsuite/lib/gdb.exp | 2 --
1 file changed, 2 deletions(-)
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index a35d08a..f21b22c 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5111,7 +5111,6 @@ gdb_caching_proc can_spawn_for_attach {
file delete $obj
gdb_test_multiple "attach $test_pid" "can spawn for attach" {
-re -wrap "Attaching to process $test_pid\r\n.*No executable file now.*" {
- pass $gdb_test_name
kill_wait_spawned_process $test_spawn_id
return 1
}
@@ -5126,7 +5125,6 @@ gdb_caching_proc can_spawn_for_attach {
return 0
}
-re -wrap "Attaching to process $test_pid\r\n.*XML support was disabled at compile time.*" {
- pass $gdb_test_name
kill_wait_spawned_process $test_spawn_id
return 1
}
--
2.1.0
next reply other threads:[~2022-03-04 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 10:15 Tiezhu Yang [this message]
2022-03-04 10:15 ` [PATCH 2/2] gdb: testsuite: fix failed testcases in gdb.base/jit-elf.exp Tiezhu Yang
2022-03-14 13:08 ` [PING] " Tiezhu Yang
2022-03-14 13:07 ` [PING] [PATCH 1/2] gdb: testsuite: remove pass statement in can_spawn_for_attach Tiezhu Yang
2022-03-16 1:21 ` Simon Marchi
2022-03-16 6:15 ` Tiezhu Yang
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=1646388927-28165-1-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=gdb-patches@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).