In message <[EMAIL PROTECTED]>, Paul Rubin wrote:
> However, the malloc problem has probably already screwed things up
> long before the application actually freezes. Your best bet is
> to recompile Python with malloc debugging enabled and/or run Python
> itself under a debugger.
A simple thing
James Stroud <[EMAIL PROTECTED]> writes:
> How do I get pdb to just run my program and spew out what's happening
> until it crashes/freezes? (This is a malloc error in a library
> somewhere and I can't figure out where--no exceptions thrown, etc.)
Maybe you want: http://docs.python.org/lib/module-
How do I get pdb to just run my program and spew out what's happening
until it crashes/freezes? (This is a malloc error in a library somewhere
and I can't figure out where--no exceptions thrown, etc.)
I think I might need to live a lot longer to simply hit 's' [enter]
until I get to the crash.
Strange. It seems to be working just fine now. Maybe I wasn't waiting
for all the symbols to be defined before setting my breakpoint.
On Nov 26, 2:41 pm, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> tac-tics wrote:
> > In the Python debugger (pdb), how do you designate breakpoints at the
> > start o
tac-tics wrote:
> In the Python debugger (pdb), how do you designate breakpoints at the
> start of methods?
> I've tried:
> break methodName
> break class.methodName
> break object.methodName
>
> but none of these seem to work. What is the trick?
define "seem to work".
the "className.methodName
In the Python debugger (pdb), how do you designate breakpoints at the
start of methods?
I've tried:
break methodName
break class.methodName
break object.methodName
but none of these seem to work. What is the trick?
--
http://mail.python.org/mailman/listinfo/python-list
