Re: saving Python process state for later debugging

2007-04-01 Thread yossi . kreinin
On Apr 1, 2:57 pm, "aspineux" wrote: > > A context in python is no more than 2 dictionaries ( globals() and > locals()). > You can easily serialize both to store them. I don't think it will work with objects defined by extension modules, except if they somehow support serialization, will it? I gue

Re: saving Python process state for later debugging

2007-04-01 Thread aspineux
On 1 avr, 09:39, [EMAIL PROTECTED] wrote: > On Apr 1, 2:07 am, "aspineux" <[EMAIL PROTECTED]> wrote: > > > > > Pylon has something like > > that.http://pylonshq.com/docs/0.9.4.1/interactive_debugger.html > > > Turbogears has the same with option tg.fancy_exception > > I could get it wrong, but the

Re: saving Python process state for later debugging

2007-03-31 Thread yossi . kreinin
On Apr 1, 2:07 am, "aspineux" <[EMAIL PROTECTED]> wrote: > > Pylon has something like > that.http://pylonshq.com/docs/0.9.4.1/interactive_debugger.html > > Turbogears has the same with option tg.fancy_exception > I could get it wrong, but these things seem to be about debugging crashed processes

Re: saving Python process state for later debugging

2007-03-31 Thread aspineux
On 31 mar, 16:48, [EMAIL PROTECTED] wrote: > Hi! > > Is there a way to save the state of a Python process for later > inspection with a debugger? One way to do this is to dump core, but is > the result usable for debugging with pdb (it can be debugged by gdb, > which can inspect PyObjects in a CPyt

saving Python process state for later debugging

2007-03-31 Thread yossi . kreinin
Hi! Is there a way to save the state of a Python process for later inspection with a debugger? One way to do this is to dump core, but is the result usable for debugging with pdb (it can be debugged by gdb, which can inspect PyObjects in a CPython core, for example, but it's not much fun)? If the