Invalid check on the result of pthread_self() leads to libpython startup failure
Open
Nobody has claimed this yet.
3.7 (EOL)
interpreter-core
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 38646 |
|---|
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-10-30.17:29:23.016>
labels = ['interpreter-core', '3.7', 'type-crash']
title = 'Invalid check on the result of pthread_self() leads to libpython startup failure'
updated_at = <Date 2019-10-30.17:29:23.016>
user = 'https://bugs.python.org/tgl'
bugs.python.org fields:
activity = <Date 2019-10-30.17:29:23.016>
actor = 'tgl'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-10-30.17:29:23.016>
creator = 'tgl'
dependencies = []
files = []
hgrepos = []
issue_num = 38646
keywords = []
message_count = 1.0
messages = ['355723']
nosy_count = 1.0
nosy_names = ['tgl']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue38646'
versions = ['Python 3.7']
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
The issue concerns the libpython startup path and an invalid check on pthread_self(), but the payload names no source file, test, or reproduction. First locate that check and establish how startup fails; done means the invalid check is addressed and libpython startup succeeds without regressing the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100