How to trace the register values of executed instructions in QEMU?
up vote
0
down vote
favorite
I can get the disassembled instructions with:
qemu-system-aarch64 -d in_asm
Sample format:
----------------
IN:
0xfffffff0: ea 5b e0 00 f0 ljmpw $0xf000:$0xe05b
----------------
IN:
0x000fe05b: 2e 66 83 3e 88 61 00 cmpl $0, %cs:0x6188
0x000fe062: 0f 85 7b f0 jne 0xd0e1
but it would also be super useful if I could see the value of the registers involved in an instruction.
For example, when loading from memory:
ldr x0, [x1]
I would like to know what value was loaded into x0
, and ideally also the value of the address that was read x1
.
Is this possible with the -d
or -trace
or some other trace mechanism?
I've seen some related old threads and it does not seem promising:
- https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg07479.html
- https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg02856.html
- https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg03057.html
I know how to do it with GDB, but a full trace would be very slow to do.
qemu
add a comment |
up vote
0
down vote
favorite
I can get the disassembled instructions with:
qemu-system-aarch64 -d in_asm
Sample format:
----------------
IN:
0xfffffff0: ea 5b e0 00 f0 ljmpw $0xf000:$0xe05b
----------------
IN:
0x000fe05b: 2e 66 83 3e 88 61 00 cmpl $0, %cs:0x6188
0x000fe062: 0f 85 7b f0 jne 0xd0e1
but it would also be super useful if I could see the value of the registers involved in an instruction.
For example, when loading from memory:
ldr x0, [x1]
I would like to know what value was loaded into x0
, and ideally also the value of the address that was read x1
.
Is this possible with the -d
or -trace
or some other trace mechanism?
I've seen some related old threads and it does not seem promising:
- https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg07479.html
- https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg02856.html
- https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg03057.html
I know how to do it with GDB, but a full trace would be very slow to do.
qemu
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I can get the disassembled instructions with:
qemu-system-aarch64 -d in_asm
Sample format:
----------------
IN:
0xfffffff0: ea 5b e0 00 f0 ljmpw $0xf000:$0xe05b
----------------
IN:
0x000fe05b: 2e 66 83 3e 88 61 00 cmpl $0, %cs:0x6188
0x000fe062: 0f 85 7b f0 jne 0xd0e1
but it would also be super useful if I could see the value of the registers involved in an instruction.
For example, when loading from memory:
ldr x0, [x1]
I would like to know what value was loaded into x0
, and ideally also the value of the address that was read x1
.
Is this possible with the -d
or -trace
or some other trace mechanism?
I've seen some related old threads and it does not seem promising:
- https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg07479.html
- https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg02856.html
- https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg03057.html
I know how to do it with GDB, but a full trace would be very slow to do.
qemu
I can get the disassembled instructions with:
qemu-system-aarch64 -d in_asm
Sample format:
----------------
IN:
0xfffffff0: ea 5b e0 00 f0 ljmpw $0xf000:$0xe05b
----------------
IN:
0x000fe05b: 2e 66 83 3e 88 61 00 cmpl $0, %cs:0x6188
0x000fe062: 0f 85 7b f0 jne 0xd0e1
but it would also be super useful if I could see the value of the registers involved in an instruction.
For example, when loading from memory:
ldr x0, [x1]
I would like to know what value was loaded into x0
, and ideally also the value of the address that was read x1
.
Is this possible with the -d
or -trace
or some other trace mechanism?
I've seen some related old threads and it does not seem promising:
- https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg07479.html
- https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg02856.html
- https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg03057.html
I know how to do it with GDB, but a full trace would be very slow to do.
qemu
qemu
edited Nov 23 at 9:40
asked Nov 23 at 9:12
Ciro Santilli 新疆改造中心 六四事件 法轮功
3,84622734
3,84622734
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1377764%2fhow-to-trace-the-register-values-of-executed-instructions-in-qemu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown