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.










share|improve this question




























    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.










    share|improve this question


























      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.










      share|improve this question















      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 at 9:40

























      asked Nov 23 at 9:12









      Ciro Santilli 新疆改造中心 六四事件 法轮功

      3,84622734




      3,84622734



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          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






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          Список кардиналов, возведённых папой римским Каликстом III

          Deduzione

          Mysql.sock missing - “Can't connect to local MySQL server through socket”