You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
My emulator in Zig was feature-complete enough to run all the reel parsing
demos
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
The text was updated successfully, but these errors were encountered:
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:
demos
code to emit the current stack trace on segfault, out of bounds, CHECK, EXIT,
or other special situations like that occurring during iVM execution
The text was updated successfully, but these errors were encountered: