Fix line number reporting in trace functions for function calls#348
Merged
blueloveTH merged 1 commit intopocketpy:mainfrom Mar 7, 2025
Merged
Fix line number reporting in trace functions for function calls#348blueloveTH merged 1 commit intopocketpy:mainfrom
blueloveTH merged 1 commit intopocketpy:mainfrom
Conversation
Collaborator
|
This is awesome. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When a trace function is set using
settrace, we can access the current file name and line number throughpy_Frame_sourceloc. However, during function calls, the line number is returned as 0. This PR fixes this issue to return the correct line number.