• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 3130 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Reading register values on FVP

Sanu5

Hello,

While executing programs on FVP (MORELLO PLATFORM MODEL target architecture is morello-purecap) with CHERIBSD OS I like to trace the register values. Any information on how to get it please.

Parents
  • 0 Arm Employee Badge in reply to Sanu5

    Ok, well my technique will only work for FVP, but your workload probably works there too. For example, you could use `run-fvp-morello-purecap` to do that, adding the extra configurations noted in my links to make tracing work.

    If you really need to use QEMU for some reason, you probably need to ask the CTSRD-CHERI team. They have a mailing list, and a public Slack channel, for example.

    If your test is small, it may be easier to simply run it under GDB (or some other debugger). You could write a GDB script to print registers periodically (or even before every instruction), for example. This approach would also work on Morello hardware.

Reply
  • 0 Arm Employee Badge in reply to Sanu5

    Ok, well my technique will only work for FVP, but your workload probably works there too. For example, you could use `run-fvp-morello-purecap` to do that, adding the extra configurations noted in my links to make tracing work.

    If you really need to use QEMU for some reason, you probably need to ask the CTSRD-CHERI team. They have a mailing list, and a public Slack channel, for example.

    If your test is small, it may be easier to simply run it under GDB (or some other debugger). You could write a GDB script to print registers periodically (or even before every instruction), for example. This approach would also work on Morello hardware.

Children
No data