Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RecursionError: maximum recursion depth exceeded in comparison #113

Open
mehdibaghery opened this issue Nov 14, 2022 · 2 comments
Open

RecursionError: maximum recursion depth exceeded in comparison #113

mehdibaghery opened this issue Nov 14, 2022 · 2 comments

Comments

@mehdibaghery
Copy link

when I want to connect QemuTarget I face to this error

@rawsample
Copy link
Member

Hello,

To help you, could you provide more context on the issue? Could you share the full backtrace? and the code so I can try to reproduce it.

@mehdibaghery
Copy link
Author

In [2]: avatar.transfer_state(ocd, qemu, synced_ranges=[ram])

RecursionError Traceback (most recent call last)
Cell In [2], line 1
----> 1 avatar.transfer_state(ocd, qemu, synced_ranges=[ram])
.
.
.

File ~/Desktop/test_venv/venv_avatar/lib/python3.10/site-packages/pygdbmi-0.10.0.2-py3.10.egg/pygdbmi/IoManager.py:236, in IoManager.write(self, mi_cmd_to_write, timeout_sec, raise_error_on_timeout, read_response)
223 """Write to gdb process. Block while parsing responses from gdb for a maximum of timeout_sec.
224
225 Args:
(...)
233 TypeError: if mi_cmd_to_write is not valid
234 """
235 # self.verify_valid_gdb_subprocess()
--> 236 if timeout_sec < 0:
237 logger.warning("timeout_sec was negative, replacing with 0")
238 timeout_sec = 0

RecursionError: maximum recursion depth exceeded in comparison

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants