Skip to content

gh-149009: Validate thread_count in profiling.sampling binary reader#149147

Merged
pablogsal merged 3 commits intopython:mainfrom
maurycy:remote-debugger-thread-count-max
May 5, 2026
Merged

gh-149009: Validate thread_count in profiling.sampling binary reader#149147
pablogsal merged 3 commits intopython:mainfrom
maurycy:remote-debugger-thread-count-max

Conversation

@maurycy
Copy link
Copy Markdown
Contributor

@maurycy maurycy commented Apr 29, 2026

The profiling.sampling binary reader reads thread_count stored in the file header but replay does not validate if there's more (thread_id, interp_id) pairs than declared.

To make it clear: that's just a validation.

Resolves gh-149009

Comment thread Modules/_remote_debugging/binary_io_reader.c
@pablogsal pablogsal enabled auto-merge (squash) May 5, 2026 00:50
@pablogsal pablogsal merged commit c266f0c into python:main May 5, 2026
60 checks passed
@pablogsal
Copy link
Copy Markdown
Member

Thanks a lot @maurycy ❤️

@maurycy maurycy deleted the remote-debugger-thread-count-max branch May 5, 2026 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

_remote_debugging: binary reader does not enforce thread_count

2 participants