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
gdb Python extensions not properly linked into new virtualenv #644
Comments
Sweet i run into that same problem, thanks so far. If it doesn't hurt it should be added. |
I meet this error, when import libpython and use py-bt: "Error occurred in Python command: init() takes exactly 3 arguments (2 given)" |
This is still an issue? I got the same problem:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions. |
Still a problem with python3.6-dbg on ubuntu 18.10 |
Seems no longer an issue as no one reported it in 3 years. |
I was playing around with virtualenv and gdb for debugging Python apps(that call out to some C libraries I wanted to inspect).
System:
Setup of virtual environment:
Testing gdb Python extended commands(fails):
This person on StackOverflow had a solution posted:
http://stackoverflow.com/questions/22931774/how-to-use-gdb-python-debugging-extension-inside-virtualenv
I'm not sure if this should be implemented in virtualenv itself if it detects a Python debug executable is being used, but this was slightly annoying/confusing to deal with and wanted to make the virtualenv team aware.
The text was updated successfully, but these errors were encountered: