From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] More suggestive displaced-stepping memory error message
Date: Wed, 11 Apr 2012 16:45:00 -0000 [thread overview]
Message-ID: <4F85A914.1050908@redhat.com> (raw)
In-Reply-To: <4F84C2D7.1070203@codesourcery.com>
On 04/11/2012 12:31 AM, Yao Qi wrote:
> Probably, GDB can be smart enough to not
> use displaced stepping when get error on accessing scratch pad. So far,
> displaced_step_prepare returns 1 for success and 0 for queued request.
> We can add one more return value -1 for `unable to do displaced
> stepping', so that caller can go non-displaced-stepping path.
We can't just go non-displaced-stepping path in non-stop with the
current code because nothing knows to pause all running threads
in order to be able to lift the breakpoint and step over it without other
threads missing it (like gdbserver knows, with linux-low.c:start_step_over
and all that). My patch #1 "all-stop on top of non-stop" patch of
the itsets series goes in that direction.
--
Pedro Alves
prev parent reply other threads:[~2012-04-11 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 19:55 Jan Kratochvil
2012-04-10 23:48 ` Yao Qi
2012-04-11 8:45 ` Jan Kratochvil
2012-04-11 9:07 ` Yao Qi
2012-04-11 15:54 ` Pedro Alves
2012-04-11 18:11 ` [commit] " Jan Kratochvil
2012-04-11 16:45 ` Pedro Alves [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=4F85A914.1050908@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=yao@codesourcery.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