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.

Author cben
Recipients cben, ezio.melotti, ncoghlan, r.david.murray
Date 2013-03-19.00:58:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363654728.46.0.181604306018.issue17475@psf.upfronthosting.co.za>
In-reply-to
Content
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?
History
Date User Action Args
2013-03-19 00:58:48cbensetrecipients: + cben, ncoghlan, ezio.melotti, r.david.murray
2013-03-19 00:58:48cbensetmessageid: <1363654728.46.0.181604306018.issue17475@psf.upfronthosting.co.za>
2013-03-19 00:58:48cbenlinkissue17475 messages
2013-03-19 00:58:48cbencreate