lp:pygdb

Created by Michael Hudson-Doyle on 2010-05-19 and last modified on 2010-11-02

This branch lets you get a combo C/Python backtrace from a Python program. Handy for figuring out issues that only happen in production!

Get your self a core file (maybe using gcore) and run python backtrace.py -c $core file.

You can also run python backtrace.py $pid to get the backtrace from a running process.

You'll need to have the python debug symbols installed (i.e. python2.6-dbg). Currently only works on 64-bit machines, but not for very deep reasons.

Get this branch:
bzr branch lp:pygdb
Members of PyGdb Hackers can upload to this branch. Log in for directions.

Related bugs

Related blueprints

Branch information

Owner:
PyGdb Hackers
Project:
pygdb
Status:
Development

Recent revisions

52. By Michael Hudson-Doyle on 2010-11-02

some hacks to give better tracebacks during interpreter teardown

51. By Michael Hudson-Doyle on 2010-10-19

load symbol table when attaching by pid; don't hardcode python version

50. By Michael Hudson-Doyle on 2010-05-19

flexibility woo

49. By Michael Hudson-Doyle on 2010-05-19

finally

48. By Michael Hudson-Doyle on 2010-05-19

argh

47. By Michael Hudson-Doyle on 2010-05-19

dum de dum de dum

46. By Michael Hudson-Doyle on 2010-05-19

dum de dum

45. By Michael Hudson-Doyle on 2010-05-19

argh

44. By Michael Hudson-Doyle on 2010-05-19

more frame info

43. By Michael Hudson-Doyle on 2010-05-19

...

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.