`start` raises exception `context: (<class 'StopIteration'>)`
See original GitHub issueDescription
Using the start
command to open an executable results in an exception : context: (<class ‘StopIteration’>).
Steps to reproduce
gdb name_of_the_binary
pwndbg> start
My setup
Gdb: 10.1 Python: 3.9.1rc1 (default, Nov 27 2020, 19:38:39) [GCC 10.2.0] Pwndbg: 1.1.0 build: bf49bf8 Capstone: 4.0.1024 Unicorn: 1.0.2
–>
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Complete Guide to Python StopIteration - eduCBA
Guide to Python StopIteration. Here we discuss how StopIteration works in python and how to avoid StopIteration exceptions with examples.
Read more >Built-in Exceptions — Python 3.11.1 documentation
When a generator or coroutine function returns, a new StopIteration instance is raised, and the value returned by the function is used as...
Read more >What is the difference between raise StopIteration and a return ...
In that context, a bare return indicates that the generator is done and will cause StopIteration to be raised. Or as @Bakuriu points...
Read more >5. Built-in Exceptions - Python 3.7.0a2 documentation
When a generator or coroutine function returns, a new StopIteration instance is raised, and the value returned by the function is used as...
Read more >The basics of generators - | notebook.community
import traceback try: next(range_generator) except StopIteration: ... Otherwise, any exceptions raised out of the generator will be propagated out (the same ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yup its working thanks 😃
@captain-woof @X3eRo0 This should be fixed on latest dev commit. Please check it out 😃