From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>, Pedro Alves <pedro@palves.net>
Subject: [PATCH v4 0/4] gdb: add gdb_attach to fix failed testcases
Date: Sat, 19 Mar 2022 10:11:23 +0800 [thread overview]
Message-ID: <1647655887-13964-1-git-send-email-yangtiezhu@loongson.cn> (raw)
Hi,
Please review this v4 patchset, thank you.
The following suggestion is very good, it needs us to do more work.
I think we can do it later after this patchset is merged into master.
https://sourceware.org/pipermail/gdb-patches/2022-March/186795.html
Tiezhu Yang (4):
gdb: testsuite: remove attach test from can_spawn_for_attach
gdb: testsuite: add new gdb_attach to check "attach" command
gdb: testsuite: use gdb_attach to fix attach-pie-noexec.exp
gdb: testsuite: use gdb_attach to fix jit-elf.exp
gdb/testsuite/gdb.base/attach-pie-noexec.exp | 5 +-
gdb/testsuite/gdb.base/jit-elf.exp | 24 ++++++----
gdb/testsuite/lib/gdb.exp | 70 ++++++++++++----------------
3 files changed, 50 insertions(+), 49 deletions(-)
--
2.1.0
next reply other threads:[~2022-03-19 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 2:11 Tiezhu Yang [this message]
2022-03-19 2:11 ` [PATCH v4 1/4] gdb: testsuite: remove attach test from can_spawn_for_attach Tiezhu Yang
2022-03-19 2:11 ` [PATCH v4 2/4] gdb: testsuite: add new gdb_attach to check "attach" command Tiezhu Yang
2022-03-21 15:00 ` Simon Marchi
2022-03-22 3:27 ` Tiezhu Yang
2022-03-19 2:11 ` [PATCH v4 3/4] gdb: testsuite: use gdb_attach to fix attach-pie-noexec.exp Tiezhu Yang
2022-03-19 2:11 ` [PATCH v4 4/4] gdb: testsuite: use gdb_attach to fix jit-elf.exp Tiezhu Yang
2022-03-21 23:04 ` [PATCH v4 0/4] gdb: add gdb_attach to fix failed testcases Kevin Buettner
2022-03-22 3:30 ` 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=1647655887-13964-1-git-send-email-yangtiezhu@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simon.marchi@polymtl.ca \
/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).