Prevent access violation on GetVarValue #269
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joaoduarte19
force-pushed
the
master
branch
from
9fa0201 to
1451d3a
Compare
martijnlaan
added a commit
that referenced
this pull request
Dec 29, 2025
Fix some dependencies between uPSC files. Fix TPSScriptDebugger.GetVarValue AV. Closes #269.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GetVarValue method caused an access violation when trying to get the value of a variable after compiling the script. The error occurs because ProcVars and ProcParams were not defined, only global variables.
Added validation fixes this error.