From: Yao Qi <qiyaoltc@gmail.com>
To: Prafull Suryawanshi <prafull.net@gmail.com>
Cc: pinskia@gmail.com, Andreas Schwab <schwab@suse.de>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Is there single step debugging support being added to aarch64-linux?
Date: Mon, 15 Jun 2015 12:51:00 -0000 [thread overview]
Message-ID: <86si9trv7l.fsf@gmail.com> (raw)
In-Reply-To: <CAJgVtDXpEWCs8oWzDcUydNA4XAQuVFrMffOk824DkTZ1cReHhQ@mail.gmail.com> (Prafull Suryawanshi's message of "Mon, 15 Jun 2015 17:18:01 +0530")
Prafull Suryawanshi <prafull.net@gmail.com> writes:
> I am not sure why hw stepper not works here (might be limitation of hw
> I am using).
You'd better to check whether hw single step doesn't work in your case.
> That is may be the infrun loops as it never gets stop signal. (the
> output I earlier pasted).
> Is it ok to provide patch for software single step like arm here?
We only implement software single step on the targets don't have
hardware single step capability, like arm.
> (I am preparing one. It will have simulate aarch64 instruction set and
> implement aarch64 version of functions of
> arm_linux_software_single_step, arm_insert_single_step_breakpoint and
> arm_get_next_pc.)
Before you start it, better to get the reason why hw single step doesn't
work on aarch64.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-06-15 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 10:21 Prafull Suryawanshi
2015-06-15 10:38 ` Andreas Schwab
2015-06-15 10:57 ` Prafull Suryawanshi
2015-06-15 11:03 ` Andreas Schwab
2015-06-15 11:07 ` Prafull Suryawanshi
2015-06-15 11:20 ` pinskia
2015-06-15 11:48 ` Prafull Suryawanshi
2015-06-15 11:57 ` pinskia
2015-06-15 12:12 ` Prafull Suryawanshi
2015-06-15 12:51 ` Yao Qi [this message]
2015-06-16 5:18 ` Prafull Suryawanshi
2015-06-16 5:22 ` Prafull Suryawanshi
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=86si9trv7l.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb@sourceware.org \
--cc=pinskia@gmail.com \
--cc=prafull.net@gmail.com \
--cc=schwab@suse.de \
/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