line traces may be missed on backward jumps when instrumented with dtrace
Open
Nobody has claimed this yet.
3.8 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33137 |
|---|---|
| Nosy | @xdegaye, @ambv, @serhiy-storchaka |
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 2018-03-25.12:01:28.011>
labels = ['interpreter-core', 'type-bug', '3.8']
title = 'line traces may be missed on backward jumps when instrumented with dtrace'
updated_at = <Date 2018-03-25.12:01:28.011>
user = 'https://github.com/xdegaye'
bugs.python.org fields:
activity = <Date 2018-03-25.12:01:28.011>
actor = 'xdegaye'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-03-25.12:01:28.011>
creator = 'xdegaye'
dependencies = []
files = []
hgrepos = []
issue_num = 33137
keywords = []
message_count = 1.0
messages = ['314408']
nosy_count = 3.0
nosy_names = ['xdegaye', 'lukasz.langa', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue33137'
versions = ['Python 3.8']
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
No source file, test, or entry point is identified. Start by reproducing the backward-jump tracing case described in BPO 33137, then locate the interpreter-core tracing path involved. Done means line traces are no longer missed when the code is instrumented with DTrace.
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