Incorrect arguments in function select() cause segfault
Open
Nobody has claimed this yet.
3.10
3.11
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
interpreter-core
topic-socket
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44718 |
|---|---|
| Nosy | @ronaldoussoren |
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 2021-07-23.04:25:27.360>
labels = ['interpreter-core', '3.8', '3.9', '3.10', '3.11', '3.7', 'type-crash']
title = 'Incorrect arguments in function select() cause segfault'
updated_at = <Date 2021-07-23.08:48:04.728>
user = 'https://bugs.python.org/xxm'
bugs.python.org fields:
activity = <Date 2021-07-23.08:48:04.728>
actor = 'ronaldoussoren'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-07-23.04:25:27.360>
creator = 'xxm'
dependencies = []
files = []
hgrepos = []
issue_num = 44718
keywords = []
message_count = 2.0
messages = ['398027', '398036']
nosy_count = 2.0
nosy_names = ['ronaldoussoren', 'xxm']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue44718'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']
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 crash at the Python interpreter's select() entry point; the issue names no source file, invocation, or test to begin with. Trace how incorrect arguments are handled and add a regression test showing that they no longer segfault, then run the relevant interpreter test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100