recent gdb versions by default won't auto-load python-gdb.py. 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?
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.
