Misc/.gdbinit:pystack is too brittle

[hydroflask]

BPO	15257
Nosy	@smontanaro, @jcea, @davidmalcolm
Files	mypatch.diff

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2018-04-05.09:16:06.294>
created_at = <Date 2012-07-05.22:40:29.785>
labels = []
title = 'Misc/.gdbinit:pystack is too brittle'
updated_at = <Date 2018-04-05.09:16:06.285>
user = 'https://bugs.python.org/hydroflask'

bugs.python.org fields:

activity = <Date 2018-04-05.09:16:06.285>
actor = 'skip.montanaro'
assignee = 'none'
closed = True
closed_date = <Date 2018-04-05.09:16:06.294>
closer = 'skip.montanaro'
components = ['Demos and Tools']
creation = <Date 2012-07-05.22:40:29.785>
creator = 'hydroflask'
dependencies = []
files = ['26263']
hgrepos = []
issue_num = 15257
keywords = ['patch']
message_count = 3.0
messages = ['164701', '222690', '314972']
nosy_count = 5.0
nosy_names = ['skip.montanaro', 'jcea', 'dmalcolm', 'BreamoreBoy', 'hydroflask']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue15257'
versions = ['Python 3.4', 'Python 3.5']

[hydroflask]

the pystack, pystackv, and printframe macros in the sample gdbinit file distributed with python are too fragile. this patch (which relies on gdb 7) is much more robust.

[BreamoreBoy]

I'm assuming that we need a patch review on this, sadly it means nothing to me.

[smontanaro]

I would prefer if these macros remain standalone (and thus fragile). Despite Python support in gdb, not everyone (more than five years after the bug report) don't use a gdb which was built --with-python. There is better support for gdb integration elsewhere in the CPython code base: Tools/gdb/libpython.py.