How to exit pdb and allow program to continue?

If you really wish to exit the debugger then you need to run something like WinPdb which allows you to detach from the process and then exit the debugger, (N.B. It is multi-platform).

If you would like to continue debugging but no longer stop at a given breakpoint then you need to:

1. Make a note of the breakpoint number, (or the file and line number),
2. Either cl bp_number or clear file:line to permanently remove the breakpoint or disable pb_number to toggle it off but be able to toggle it back.
3. Then continue and your program run until then next different breakpoint is hit.

For more detail on the above see the manual.

A simple Ctrl–D will break out of pdb. If you want to continue rather than breaking, just press c rather than the whole continue command

The answer from @voithos is correct, so I’ll just add one alternative in the case where you are using set_trace. Yes, the pdb.set_trace = lambda: None hack works OK, but not if you have other breakpoints set and want to reenable it later on. To me this points to the fact that unfortunately pdb is missing a bunch of functionality (even basic stuff like display lists), and this is another case.

The good news is that pdb++ is a great drop-in replacement for pdb, and one of the things it solves is exactly the problem of disabling set_trace. So you can simply do:

pip install pdbpp

and then at the (Pdb++) prompt, type:

pdb.disable()

If you want to reenable later, unsurprisingly this works:

pdb.enable()

Easy! And you will get lots of other useful goodies on top of that.

find new way to exit the pdb without install anything:
– when the program starts to run, press ctrl+c, then switch the window to another(any window), then the original shell with pdb running should show
something like: (pdb) …..
– switch back to pdb, then press Enter, now you are all set, pdb command
shell reappear again

Disable the breakpoint. from pdb, just type disable N, where N is the breakpoint number you are stuck on. If you don’t know the number of your troubling breakpoint, enter tbreak. This will list your breakpoints by number under column "Num" and show whether (yes) or not (no) they are enabled or disabled under the column headed with "Enb."

Once you disbale your troubling breakpoint, running the command continue (or the abbreviation c) should finish your program.

If you used breakpoint() in your code, you can disable all those breakpoints by environment variable.

import os
os.environ['PYTHONBREAKPOINT'] = '0'

This also work when you are in (Pdb) interactive state, this will disable all breakpoint() inserted in your code, but not breakpoints enabled by (Pdb).

So lets test this, code have breakpoint() in line 4:

> /tmp/py.py(5)<module>()
-> print(x,a)
(Pdb) ll
  1     
  2     for x in "abcdefg":
  3         a=1
  4         breakpoint()
  5  ->     print(x,a)
  6         b=2
  7         print(x,b)

Lets set new breakpoint in line 6.

(Pdb) break 6
Breakpoint 1 at /tmp/py.py:6

(Pdb) break
Num Type         Disp Enb   Where
1   breakpoint   keep yes   at /tmp/py.py:6

Now lets disable all breakpoint() in this case in line 4.

(Pdb) import os
(Pdb) os.environ['PYTHONBREAKPOINT'] = '0'

and continue

(Pdb) c
a 1
> /tmp/py.py(6)<module>()
-> b=2
(Pdb) ll
  1     
  2     for x in "abcdefg":
  3         a=1
  4         breakpoint()
  5         print(x,a)
  6 B->     b=2
  7         print(x,b)

now it stops in line 6 and skip line 4, lets continue

(Pdb) c
a 2
b 1
> /tmp/py.py(6)<module>()
-> b=2

now it stops again in line 6 and skip line 4

(Pdb) break
Num Type         Disp Enb   Where
1   breakpoint   keep yes   at /tmp/py.py:6
(Pdb) clear 1
Deleted breakpoint 1 at /tmp/py.py:6

now (Pdb) breakpoint in line 6 is deleted and program can continue working:

(Pdb) c
b 2
c 1
c 2
d 1
d 2
e 1
e 2
f 1
f 2
g 1
g 2

I was stuck in a pdb shell, with Enter just producing ^M, so I couldn’t escape it.

After some scientifically-crafted experimentation, turns out ctrl+Z haults the pdb shell. (Then stty sane to fix the Enter key.)

Then you need to kill or resume the pdb shell. To do so, run jobs, then either fg 1 or kill %1 (substituting the job number).

Figured I’d note it here for any others, and myself when I’m back here next week.

• hit c -> for continue (executes your program further)
• hit q -> for quit (exit debugger and your program as well)