From: Tom Tromey <tom@tromey.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: LoongArch: prepend tramp frame unwinder for signal
Date: Mon, 04 Apr 2022 10:43:50 -0600 [thread overview]
Message-ID: <87h778kddl.fsf@tromey.com> (raw)
In-Reply-To: <1648728080-10984-1-git-send-email-yangtiezhu@loongson.cn> (Tiezhu Yang's message of "Thu, 31 Mar 2022 20:01:20 +0800")
>>>>> Tiezhu Yang <yangtiezhu@loongson.cn> writes:
> Implement the "init" method of struct tramp_frame to prepend tramp
> frame unwinder for signal on LoongArch.
> With this patch, the following failed testcases can be fixed:
> FAIL: gdb.base/annota1.exp: backtrace @ signal handler (timeout)
> FAIL: gdb.base/annota3.exp: backtrace @ signal handler (pattern 2)
Thank you for the patch. This is ok, though as loongarch maintainer you
can self-approve patches that only touch this port's files.
Because LoongArch is a new port, I think it's fine if you want to apply
this to the gdb 12 branch as well.
Tom
next prev parent reply other threads:[~2022-04-04 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:01 Tiezhu Yang
2022-04-04 16:43 ` Tom Tromey [this message]
2022-04-06 3:18 ` Tiezhu Yang
2022-04-06 14:56 ` Tom Tromey
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=87h778kddl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=yangtiezhu@loongson.cn \
/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).