From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/4] gdb: add gdb_attach to fix failed testcases
Date: Fri, 18 Mar 2022 09:53:05 +0800 [thread overview]
Message-ID: <c5bbca93-f543-0aca-461c-88f9311b1253@loongson.cn> (raw)
In-Reply-To: <7807b618-33b2-1e6c-e618-bf477c2b145e@palves.net>
On 03/18/2022 12:55 AM, Pedro Alves wrote:
> On 2022-03-17 14:00, Tiezhu Yang wrote:
>> Hi Simon and Pedro,
>>
>> Thank you very much for your suggestions.
>> Please review this v3 patchset.
>> Any comments will be much appreciated.
>
> Thanks for doing this.
>
> Are these really the only .exp files that need to use gdb_attach? Or is it just
> that you're tackling this incrementally?
>
At least for now, attach-pie-noexec.exp and jit-elf.exp need to use
gdb_attach to fix the failed testcases, if we find the other .exp
files also have similar issues in the future, I will tackling them
incrementally.
Thanks,
Tiezhu
next prev parent reply other threads:[~2022-03-18 1:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 14:00 Tiezhu Yang
2022-03-17 14:00 ` [PATCH v3 1/4] gdb: testsuite: remove attach test from can_spawn_for_attach Tiezhu Yang
2022-03-17 14:00 ` [PATCH v3 2/4] gdb: testsuite: add new gdb_attach to check "attach" command Tiezhu Yang
2022-03-17 16:50 ` Pedro Alves
2022-03-17 17:04 ` Simon Marchi
2022-03-17 17:31 ` Pedro Alves
2022-03-18 1:56 ` Tiezhu Yang
2022-03-18 18:23 ` Simon Marchi
2022-03-17 14:01 ` [PATCH v3 3/4] gdb: testsuite: use gdb_attach to fix attach-pie-noexec.exp Tiezhu Yang
2022-03-17 16:51 ` Pedro Alves
2022-03-17 14:01 ` [PATCH v3 4/4] gdb: testsuite: use gdb_attach to fix jit-elf.exp Tiezhu Yang
2022-03-17 16:55 ` [PATCH v3 0/4] gdb: add gdb_attach to fix failed testcases Pedro Alves
2022-03-18 1:53 ` Tiezhu Yang [this message]
2022-03-18 18:33 ` Pedro Alves
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=c5bbca93-f543-0aca-461c-88f9311b1253@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).