From: Yao Qi <yao@codesourcery.com>
To: Chung-Lin Tang <cltang@codesourcery.com>
Cc: <gdb-patches@sourceware.org>,
Thomas Schwinge <thomas_schwinge@mentor.com>
Subject: Re: [PATCH][SH] Signal handler unwinding for SH-Linux
Date: Sun, 29 Apr 2012 15:16:00 -0000 [thread overview]
Message-ID: <4F9D3BA4.5090307@codesourcery.com> (raw)
In-Reply-To: <4F9CF631.9080807@codesourcery.com>
On 04/29/2012 04:05 PM, Chung-Lin Tang wrote:
> The test results show improvement on many sighandler related tests, with
> no regressions. Some gdb.base/sigbpt.exp tests change from FAIL->KFAIL,
> though I'm not completely sure what that indicates.
Chung-Lin,
Not sure the comment at the beginning of gdb.base/sigbpt.exp is relevant
to your KFAILs.
# This test is known to tickle the following problems: kernel letting
# the inferior execute both the system call, and the instruction
# following, when single-stepping a system call; kernel failing to
# propogate the single-step state when single-stepping the sigreturn
# system call, instead resuming the inferior at full speed; GDB
# doesn't know how to software single-step across a sigreturn
# instruction. Since the kernel problems can be "fixed" using
# software single-step this is KFAILed rather than XFAILed.
If this comment is related to your KFAILs, this can be handled by
computing the "next pc" of sigreturn or rt_sigreturn. Please have a
look at functions {arm,mips,tic6x}_linux_syscall_next_pc. You can do
something similar in SH backend. Hope it helps.
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-04-29 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 8:58 Chung-Lin Tang
2012-04-29 15:16 ` Yao Qi [this message]
2012-05-02 21:52 ` Joel Brobecker
2012-05-07 13:19 ` Chung-Lin Tang
2012-05-07 15:36 ` Joel Brobecker
2012-05-07 15:44 ` Chung-Lin Tang
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=4F9D3BA4.5090307@codesourcery.com \
--to=yao@codesourcery.com \
--cc=cltang@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=thomas_schwinge@mentor.com \
/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