This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Better doc on using python-gdb.py
Type: enhancement Stage: resolved
Components: Devguide Versions:
process
Status: closed Resolution: duplicate
Dependencies: Superseder:
Assigned To: Nosy List: cben, dmalcolm, ezio.melotti, ncoghlan, r.david.murray, vstinner, willingc
Priority: normal Keywords: patch

Created on 2013-03-19 00:58 by cben, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
python-gdb-how-to-load.diff cben, 2013-03-19 00:58
Messages (4)
msg184574 - (view) Author: Cherniavsky Beni (cben) * Date: 2013-03-19 00:58
recent gdb versions by default won't auto-load python-gdb.py.
issue15043 fixed this in test_gdb, but manual action is still needed to when a developer actually wants to run gdb.

Attached devguide patch.
After writing this I noticed it's already explained in faq.txt, but I think it's important to also explain it in the devguide's GDB section.

Should this also be mentioned inside python-gdb.py?
And why does that file have a Tools/gdb/libpython.py doppleganger?
msg184578 - (view) Author: Cherniavsky Beni (cben) * Date: 2013-03-19 01:08
The links to gdb docs presently are broken because sourceware.org is down for maintenance, but it should be back up in a couple days.
msg184629 - (view) Author: Ezio Melotti (ezio.melotti) * (Python committer) Date: 2013-03-19 10:42
The last part is not clear to me.  Do you mean that if I don't add the "add-auto-load-safe-path" I have to run "source python-gdb.py" before "gdb python"?  And if so, do I have to run it every time?
Also if the "add-auto-load-safe-path" is required for recent versions, maybe it should be documented first, and you can then mention that older versions might work even without it.
msg241409 - (view) Author: Carol Willing (willingc) * (Python committer) Date: 2015-04-18 11:01
The current devguide on gdb (https://docs.python.org/devguide/gdb.html?highlight=gdb) satisfies this issue.

I am marking this languishing issue as a duplicate and closing it.
History
Date User Action Args
2022-04-11 14:57:43adminsetgithub: 61677
2015-04-22 02:36:29willingcsetstatus: open -> closed
2015-04-18 11:01:23willingcsetnosy: + willingc
messages: + msg241409

resolution: duplicate
stage: patch review -> resolved
2013-03-19 10:42:19ezio.melottisettype: enhancement
stage: patch review
messages: + msg184629
versions: - Python 3.4
2013-03-19 02:37:54vstinnersetnosy: + vstinner
2013-03-19 01:11:02r.david.murraysetnosy: + dmalcolm
2013-03-19 01:08:43cbensetmessages: + msg184578
2013-03-19 00:58:48cbencreate