Description of problem: The gdb init script shipped with the python-devel package has lots of useful commands for working out where we are in the Python source script and so on. If the crash application is python it would be great if abrt used some of these to point to where in the Python program it crashed. Just having the interpreter's stack trace isn't so useful. It isn't usually the interpreter at fault.
Can you be more specific? Is the bug is that - python-devel gdb plugin doesn't load? or - it loads all right, but abrt doesnt use any cool and useful commands it provides when it generates a backtrace? And if so, which exactly commands do you want abrt to run in gdb? (I'm no expert on gdb-on-python, sorry)
I'm no expert on it either. Looks like abrt would need to run extra commands, perhaps something like 'pystackv' -- in addition to loading the plugin in the first place.
I thought it's loaded automatically, CCing dmalcolm as he should be expert on this.
It isn't loaded automatically, but it's been superseded for gdb 7 onwards by the gdb Python script I wrote for Python itself. See: http://fedoraproject.org/wiki/Features/EasierPythonDebugging From Fedora 13 onwards, a regular "bt" in gdb should show Python-level information from a stack track involving the Python interpreter, assuming that python-debuginfo is installed (similar for python3-debuginfo). This has been working for me with abrt crash reports for Python since then.
See also the notes I wrote for upstream here: http://docs.python.org/devguide/gdb.html
Indeed, thanks.