public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra@codesourcery.com>
To: Yao Qi <qiyaoltc@gmail.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix PR 8841 for nios2-linux
Date: Thu, 19 Oct 2017 17:37:00 -0000	[thread overview]
Message-ID: <59E8E2CA.5030906@codesourcery.com> (raw)
In-Reply-To: <1508154626-389-1-git-send-email-yao.qi@linaro.org>

On 10/16/2017 05:50 AM, Yao Qi wrote:
> This patch is to use gdbarch method code_of_frame_writable, to skip
> signal trampoline frame for breakpoint setting on nios2-linux.  The patch
> was written last year, but forgot to upstream it.
>
> I don't have the env to test this patch, so Sandra could you try this
> patch?
>
> gdb:
>
> 2017-10-16  Yao Qi  <yao.qi@linaro.org>
>
> 	PR gdb/8841
> 	* nios2-linux-tdep.c (nios2_linux_code_of_frame_writable): New
> 	function.
> 	(nios2_linux_init_abi): Install gdbarch code_of_frame_writable.

Thanks for looking at this!  :-)  The patch does seem to have the 
intended behavior for "finish", but there are multiple new FAILs in the 
test case sigaltstack.exp, which hasn't been adjusted to know that it's 
valid for "finish" to skip frames.  Plus that test has KFAILs for the 
existing behavior of being unable to set the breakpoint at an unwritable 
address that ought to be removed, too.

It also looks like this fix doesn't work for "step" out of a signal 
handler -- this shows up in sigstep.exp.  And there are new FAILs in 
that testcase where "finish" is doing unexpected things now too.

-Sandra

      reply	other threads:[~2017-10-19 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 11:50 Yao Qi
2017-10-19 17:37 ` Sandra Loosemore [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=59E8E2CA.5030906@codesourcery.com \
    --to=sandra@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).