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
Improve gdbinit of Python 2.6 #47881
Comments
I wrote a patch to improve gdbinit (gdb macros):
See also bpo-3610 (for Python 3.0). |
Thanks for the patch. Most of it looks okay except for the rewrite of |
@Skip: oh yes, you're right about the core file :-) So forget the |
Gdb7 now supports Python as a script language, and Python trunk/py3k has a gdb library to debug Python programs. It's much better than the old Misc/gdbinit script. Close this issue as "out of date". |
It's too bad this is closed out of date because I spent a few hours of my life figuring out why it fails and writing an alternative implementation that works for me. Instead of just closing this ticket, something should be done about the distributions of python so that they don't suggest something that you consider outdated and doesn't actually work. Here's my working version, for reference: # THOMAS: the test for between Py_Main and Py_GetArgcArgv is because # in 2.6, PyEval_EvalFrame is only bw compatible, and code now calls
end |
fyi - for information on using gdb 7 with python see http://bugs.python.org/issue8032 I'm looking at the .gdbinit improvements regardless as not everyone has gdb 7 (notably OS X). |
everything except the lineno change from gdbinit_python26.patch has been committed in r85646. |
and the py_decref in there isn't quite right, fixing... |
I think the reference to EasierPythonDebugging is outdated and should be corrected. Dave Malcolm's work is already part of Python, and available with every Python build. |
do we have official python docs on this that I should point to? |
I only know of the doc string of libpython.py itself, in Tools/gdb |
I updated the note in gdbinit to point to Tools/gdb/libpython.py for py3k (3.2) and 2.7. Thomas: I didn't do anything with your version of pystack because the existing versions in 3.2 and 2.7 appear to work fine for me. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: