gdb debugging python frames in optimised interpreters

[mcobden]

BPO	17558
Nosy	@davidmalcolm

^{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 = None
created_at = <Date 2013-03-27.14:32:18.142>
labels = ['type-feature']
title = 'gdb debugging python frames in optimised interpreters'
updated_at = <Date 2013-07-09.21:07:07.229>
user = 'https://bugs.python.org/mcobden'

bugs.python.org fields:

activity = <Date 2013-07-09.21:07:07.229>
actor = 'mcobden'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Demos and Tools']
creation = <Date 2013-03-27.14:32:18.142>
creator = 'mcobden'
dependencies = []
files = []
hgrepos = []
issue_num = 17558
keywords = []
message_count = 2.0
messages = ['185337', '192779']
nosy_count = 2.0
nosy_names = ['dmalcolm', 'mcobden']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17558'
versions = ['Python 2.7']

[mcobden]

I've made some tweaks to the libpython.py util functions to better pick up python frames when using a normal python interpreter.

It's not by any means perfect, but it works on my ubuntu-shipped python interpreter (with debugging symbols installed, but not running the debug interpreter).

It works by finding the top frame via the thread state struct, and then going up the frame stack, comparing the stack pointer to a stack pointer in the C context.

I'd appreciate some feedback/advice :)

https://gist.github.com/leth/5254239/revisions

[mcobden]

Is there anyone who could take a look at this? I'd rather it not bit-rot into oblivion.

I know the code quality is rather poor, but I can fix that.