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

Keep track of callstack #502

Merged
merged 1 commit into from
Nov 16, 2024
Merged

Keep track of callstack #502

merged 1 commit into from
Nov 16, 2024

Conversation

kengorab
Copy link
Owner

Whenever a function is called, a 64-bit integer value is pushed onto an "array" - this array is actually just a stack-allocated global of bytes that is meant to emulate the callstack. The 64-bit integer represents an encoding of the function being called, the file in which it was called, and the line within that file on which it was called. After the function returns, the value is "popped" from this array.

Whenever a function is called, a 64-bit integer value is pushed onto an
"array" - this array is actually just a stack-allocated global of bytes
that is meant to emulate the callstack. The 64-bit integer represents an
encoding of the function being called, the file in which it was called,
and the line within that file on which it was called. After the function
returns, the value is "popped" from this array.
@kengorab kengorab merged commit 11686ea into master Nov 16, 2024
1 check passed
@kengorab kengorab deleted the callstack branch November 16, 2024 01:49
@kengorab
Copy link
Owner Author

This closes #483

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant