gh-131296: fix clang-cl warning in tracemalloc.c - #131514
Merged
vstinner merged 1 commit intoMar 22, 2025
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Always set MAX_NFRAME to UINT16_MAX. Avoid the complicated code which emitted a compiler warning.
Copy link
Copy Markdown
Member
Author
|
65535 is already the effective limit: $ python Python 3.13.2 (main, Feb 4 2025, 00:00:00) [GCC 14.2.1 20250110 (Red Hat 14.2.1-7)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import tracemalloc; tracemalloc.start(2**16+1) Traceback (most recent call last): ValueError: the number of frames must be in range [1; 65535] |
Sorry, something went wrong.
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
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.
Always set MAX_NFRAME to UINT16_MAX.
Avoid the complicated code which emitted a compiler warning.