`_remote_debugging`: No frame limit in `get_async_stack_trace()`
Open
Nobody has claimed this yet.
extension-modules
topic-profiling
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
We've got it in process_frame_chain():
There's no such limit in parse_async_frame_chain():
CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS
Linked PRs
- gh-153365
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Modules/_remote_debugging/frames.c at process_frame_chain() and compare its frame-limit handling with parse_async_frame_chain() and the related paths in Modules/_remote_debugging/asyncio.c. Done means the async stack-trace path enforces the same frame limit; check linked PR gh-153365 before beginning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100