Trepan-Debuggers / Trepan-Debuggers/python3-trepan
"Weird termination bug" occurring inconsistently.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
As I hinted at in https://github.com/rocky/python3-trepan/issues/22#issuecomment-1219634096, my use of breakpoint() to enter the debugger seems to be causing a strange error on termination. It seems similar to the issue fixed in 68474af585b7a1c4547ba912feb9c72cfb3cae42, as it points at a tracer.py line with inspect.currentframe with an AttributeError for that access. No such error appears if I debug using the trepan3k binary.
Contributor guide
No contributing guide indexed for this repository
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 reviewing issue #22's referenced comment and commit 68474af585b7a1c4547ba912feb9c72cfb3cae42, then inspect the tracer.py path involving inspect.currentframe. Reproduce termination after entering the debugger with breakpoint(), compare it with the trepan3k binary, and consider the issue done when the intermittent AttributeError no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100