[Python-bugs-list] [ python-Bugs-634116 ] pdb quit breakage

SourceForge.net noreply@sourceforge.net
Fri, 31 Jan 2003 13:07:57 -0800


Bugs item #634116, was opened at 2002-11-05 17:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=634116&group_id=5470

Category: Python Library
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Guido van Rossum (gvanrossum)
Assigned to: Nobody/Anonymous (nobody)
Summary: pdb quit breakage

Initial Comment:
Behold:

>>> import pdb
>>> pdb.run("pass")
> <string>(1)?()
(Pdb) q
>>> pdb.run("pass")
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "/usr/local/lib/python2.3/bdb.py", line 48, in
trace_dispatch
    return self.dispatch_line(frame)
  File "/usr/local/lib/python2.3/bdb.py", line 61, in
dispatch_line
    if self.quitting: raise BdbQuit
bdb.BdbQuit
>>> pdb.run("pass")
> <string>(1)?()
(Pdb) q
>>> 

IOW, quitting out of pdb causes some sticky state to
remain behind which sabotages the next call to pdb.run(). 

This bug is new in Python 2.3.

----------------------------------------------------------------------

>Comment By: Guido van Rossum (gvanrossum)
Date: 2003-01-31 16:07

Message:
Logged In: YES 
user_id=6380

WFM too now. Maybe the latest checkin (by mwh) to pdb.py
fixed it.

----------------------------------------------------------------------

Comment By: Michael Stone (mbrierst)
Date: 2003-01-31 15:57

Message:
Logged In: YES 
user_id=670441

This is very odd.  I just downloaded the latest cvs and do not see the problem.  Is it still there?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=634116&group_id=5470