public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH v4 0/4] gdb: add gdb_attach to fix failed testcases
Date: Tue, 22 Mar 2022 11:30:48 +0800	[thread overview]
Message-ID: <94f3ffbf-7bd4-a2e0-b949-3bc738748af6@loongson.cn> (raw)
In-Reply-To: <20220321160448.765329e2@f35-zws-1>



On 03/22/2022 07:04 AM, Kevin Buettner wrote:
> On Sat, 19 Mar 2022 10:11:23 +0800
> Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>
>> Please review this v4 patchset, thank you.
>
> FWIW, my testing shows that this series fixes problems introduced
> by commit 1dbf27133db.
>
> It eliminates the new failure in gdb.base/run-after-attach.exp and
> three failures in a new test that I'm working on.
>
> Kevin
>

Thank you for your test and feedback.

I will do a small change of patch #2 suggested by Simon,
and then I will send v5 soon.

Thanks,
Tiezhu


      reply	other threads:[~2022-03-22  3:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19  2:11 Tiezhu Yang
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 [this message]

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=94f3ffbf-7bd4-a2e0-b949-3bc738748af6@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --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).