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.

Sign up for GitHub

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

Jump to bottom

EVT backtraces #38

Open
bates64 opened this issue Feb 4, 2024 · 1 comment
Open

EVT backtraces #38

bates64 opened this issue Feb 4, 2024 · 1 comment
Labels
feature New engine feature

Comments

@bates64
Copy link
Owner

bates64 commented Feb 4, 2024 •
edited
Loading

If a crash happens in a script, we should show the script that crashed rather than the evt_execute_next_command trace
@bates64 bates64 added the feature New engine feature label Feb 4, 2024
@bates64 bates64 mentioned this issue Feb 5, 2024
Merged
@z64a
Copy link
Collaborator

z64a commented Feb 5, 2024

Added EvtCallingLine in evt.c which is NULL except when an EVT_CALL is being processed. When a crash occurs, check this variable and if it isn't NULL it will point to the line in the script which triggered the crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New engine feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bates64 @z64a