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

Extending multiple emulators to support my stack trace instrumentation scheme #11

Open
trgwii opened this issue Nov 29, 2024 · 0 comments

Comments

@trgwii
Copy link
Member

trgwii commented Nov 29, 2024

If I start doing this I will open relevant PR's in
yafie or others.

I currently have an uncommitted instrumentation outputter and parser, meaning I
can inject code into each callsite and return statement in any code compiled to
ivm, to cause it to output the address of the currently called or returned-from
function.

This means that an out-of-VM process (the parser) can take this information and
convert it to symbols via the .sym file (holding all the symbol addresses).

Following this scheme it would be useful if either:

  1. My emulator in Zig was feature-complete enough to run all the reel parsing
    demos
  2. The yet-another-fast-ivm-emulator was changed so it would output the control
    code to emit the current stack trace on segfault, out of bounds, CHECK, EXIT,
    or other special situations like that occurring during iVM execution
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant