From: "chengjian (D)" <cj.chengjian@huawei.com>
To: Will Deacon <will.deacon@arm.com>
Cc: <catalin.marinas@arm.com>, <oleg@redhat.com>,
<linux@armlinux.org.uk>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
"Xiexiuqi (Xie XiuQi)" <xiexiuqi@huawei.com>,
Li Bin <huawei.libin@huawei.com>
Subject: Re: A issue about ptrace/SINGLESTEP on arm64
Date: Tue, 17 Oct 2017 10:04:00 +0800 [thread overview]
Message-ID: <d8b5e71d-f8db-bee0-dadf-c57724a68daa@huawei.com> (raw)
In-Reply-To: <20171016153055.GD10500@arm.com>
On 2017/10/16 23:30, Will Deacon wrote:
> Can you jump the PC once the child appears to be "stuck"?
>
> IIRC, GDB has special heuristics to step through LDXR/STXR critical
> sections.
The function can be returned, But the number of instructions looks too much
We use objdump to count the assembly code length of the program
#=======
#trace
#=======
ptrace/2-arm64-loop # objdump -d ./nop | wc -l
115885
ptrace/2-arm64-loop # ./ptrace_singlestep ./nop
./nop : nop
Please wait
Number of machine instructions : 186688022
/ptrace/2-arm64-loop # ./ptrace_singlestep ./nop
./nop : nop
Please wait
Number of machine instructions : 103670668
The number of instructions executed twice is not the same
#=======
#trace ls
#=======
ptrace/2-arm64-loop # objdump -d /bin/ls | wc -l
18095
ptrace/2-arm64-loop # ./ptrace_singlestep /bin/ls
/bin/ls : ls
Please wait
Number of machine instructions : 7718122167
It seems that the child has also been tracked by the parent process
when it goes into the kernel space.
Is this what your 'stuck' mean?
Does all the instructions been tracked in kernel space, or only the
LDXR/STXR?
next prev parent reply other threads:[~2017-10-17 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 4:27 chengjian (D)
2017-10-16 15:30 ` Will Deacon
2017-10-17 2:04 ` chengjian (D) [this message]
2017-10-17 9:23 ` Will Deacon
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=d8b5e71d-f8db-bee0-dadf-c57724a68daa@huawei.com \
--to=cj.chengjian@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=huawei.libin@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=oleg@redhat.com \
--cc=will.deacon@arm.com \
--cc=xiexiuqi@huawei.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
all inboxes | Powered by JetHome®