Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

consider documenting how to detect capability memory tramples #349

Open
tariqkurd-repo opened this issue Aug 28, 2024 · 0 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@tariqkurd-repo
Copy link
Collaborator

Something which came up in the past in the difficulty of debugging accidental memory tramples which clear memory tags.

  1. set up a trigger on the capability which is losing its tag
  2. wait for trigger match, which executes beforfe the trample
  3. load data from the address, and get the tag
  4. single-step to execute the trampling store
  5. read again to get the new tag to see if it has cleared

it maybe be worth putting this in an appendix in the spec as a suggested debugging sequence possibly with some examples.

@tariqkurd-repo tariqkurd-repo added the documentation Improvements or additions to documentation label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant