[issue3632] use string_print() in gdb

[Amaury Forgeot d'Arc]

Amaury Forgeot d'Arc <amauryfa at gmail.com> added the comment:

I once fell into the same issue, but the patch should modify
_PyObject_Dump(), around the call to PyObject_Print.

string_print() is not the only function called by _PyObject_Dump, by far...

And beware that many people routinely run python in "debug mode" outside
gdb, for example during development.
That's why it's better to modify _PyObject_Dump only; we can be sure
that it only affects a debugger session.

----------
nosy: +amaury.forgeotdarc

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3632>
_______________________________________