[issue3632] use string_print() in gdb

Amaury Forgeot d'Arc added the comment: Committed in r67802. -- resolution: accepted -> fixed status: open -> closed ___ Python tracker ___ __

[issue3632] use string_print() in gdb

STINNER Victor added the comment: Can anyone apply this patch? Or explain me why it can not be applied? ___ Python tracker ___ ___ Python-bugs-

[issue3632] use string_print() in gdb

Daniel Diniz <[EMAIL PROTECTED]> added the comment: I would love to have this patch, along with those of #3631 and #3610, included in Misc as diffs. This would make it easier to get the improved functionality in a new development box, besides allowing distributions to apply them at will. ---

[issue3632] use string_print() in gdb

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The patch is fine. I don't know if it can make the 2.6 release, but it is very simple, and affect only a function used in debugger macros. -- resolution: -> accepted ___ Python tracker <[EMA

[issue3632] use string_print() in gdb

STINNER Victor <[EMAIL PROTECTED]> added the comment: Can anyone review my new patch? ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue3632] use string_print() in gdb

Changes by STINNER Victor <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11192/string_print.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3632] use string_print() in gdb

Changes by STINNER Victor <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file11193/pyobject_dump.patch ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3632] use string_print() in gdb

STINNER Victor <[EMAIL PROTECTED]> added the comment: Oh! I have a better idea: why not patching _PyObject_Dump() instead of string_print() :-) So here is a new patch. ___ Python tracker <[EMAIL PROTECTED]> _

[issue3632] use string_print() in gdb

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> 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 pyt

[issue3632] use string_print() in gdb

New submission from STINNER Victor <[EMAIL PROTECTED]>: "pyo" macro from gdbinit (see #3631) uses _PyObject_Dump() to display an object. This function calls (indirectly) string_print() to display one line of text. But if the GIL is released (I guess it's the GIL or is it called the "thread sta