David> In particular, for scripting languages,
David> it's most useful to be able to extract the script-level backtrace from
David> the C-level stack (i.e. "what was the Python code doing?")
Tom> FWIW we're adding direct support for this to gdb.
Tom> You'll be able to supply backtrace filters with your project just as you
Tom> currently can provide value and type pretty-printers.
Jiri> Does it mean just dropping a python script to some directory and GDB
Jiri> will call this script when processing a specific coredump? Or does the
Jiri> caller (abrt or user) have to manually instruct gdb to use it?
It will work just like pretty printers -- so, automatic if that is what
the package maintainers want to do.
At least, that is the situation for CLI users.
MI clients will have to request the new behavior, because it changes MI