"Weird termination bug" occurring inconsistently.

Open
#44 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
devtools

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.

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.

Dominant language
Python
Stars
176
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Trepan-Debuggers/python3-trepan

All issues in Trepan-Debuggers/python3-trepan

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.