python 2.3a1 pdb broken? or is it a feature?

Changjune Kim juneaftn at REMOVETHIShanmail.net
Sat Jan 11 02:01:11 CET 2003


"Jane Austine" <janeaustine50 at hotmail.com> wrote in message
news:ba1e306f.0301090952.2a5fe0ba at posting.google.com...
> I'm running python 2.3a1 on a Win32 machine.
>
> pdb's behaviour seems to have been changed from 2.2*.
>

Yes.

> "user_call" method is added, and it's called automatically
> for every function/method call when I set a breakpoint somewhere
> else and "continue".
>

It had been omitted but now is overridden in 2.3a1.

> For example:
>
> <foobar.py>
> ------------------------
> def a():
>     print "a..."
>     b()
> def b():
>     print "b..."
>     c()
> def c():
>     print "c..."
>
> -------------------------
> >>> pdb.run("a()")
> ...
> (Pdb) b foobar:2
> Breakpoint 1 at foobar.py:2
> (Pdb) c
> --Call--
> > c:\...\foobar.py(1)a()
> -> def a():
> (Pdb) cont
> > c:\...\foobar.py(2)a()
> -> print "a..."
> (Pdb) continue
> a...
> --Call--
> > c:\...\foobar.py(4)b()
> -> def b():
> (Pdb)
>
> I desparately want to Continue.

user_call is called whenever there is _any_ break and the
running point enters a function/method.

I don't have a clue for what reason user_call method is overridden by
default
in pdb.py now but you could inherit and "pass" it or simply comment it out.

>
> Jane





More information about the Python-list mailing list