New submission from Cherniavsky Beni: 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? ---------- components: Devguide files: python-gdb-how-to-load.diff keywords: patch messages: 184574 nosy: cben, ezio.melotti, ncoghlan, r.david.murray priority: normal severity: normal status: open title: Better doc on using python-gdb.py versions: Python 3.4 Added file: http://bugs.python.org/file29469/python-gdb-how-to-load.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17475> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
