Leak sanitizer errors when `--enable-profiling` is passed to `configure` during build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
Configure command: ./configure -C --disable-gil --enable-optimizations --with-address-sanitizer --with-undefined-behavior-sanitizer --enable-experimental-jit=interpreter --enable-shared --enable-profiling --enable-safety --enable-bolt --enable-pystats --with-pydebug --with-assertions --with-lto=yes --with-strict-overflow with Ubuntu 24.04 and GCC 13.3.0
Build log:
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
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 by reproducing the CPython main-branch build on Linux with the reported configure command, focusing on the interaction between --enable-profiling and the sanitizer options. The issue is ready when the build no longer leaks sanitizer errors with profiling enabled and the relevant build output demonstrates the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100