.. _jgdv.debugging.running_debugger:
   
    
===============================
jgdv.debugging.running_debugger
===============================
  

   
.. py:module:: jgdv.debugging.running_debugger

       
 

   
 

 

 
   
        

           

 
 

           
   
             
  
           
 
  
 
 
  

   
Classes
-------
  


.. autoapisummary::

    jgdv.debugging.running_debugger.RunningDebugger
           
 
      
 
Module Contents
===============

 
 

.. _jgdv.debugging.running_debugger.RunningDebugger:
   
.. py:class:: RunningDebugger
   
    
   The usual debugger stops execution when you call it.
   This starts the tracing, without pausing execution.
   so on a future breakpoint, you can pause and have a trace from where you started the debugger

   
      
   .. py:method:: do_help(*args) -> <Unknown>
      


      
   .. py:method:: precmd(line) -> <Unknown>
      


      
   .. py:method:: set_running_trace(frame=None) -> <Unknown>
      

      Start debugging from frame, without pausing execution.
      This is to allow setting a future breakpoint, without having
      to enter the debugger and exit again.



      
   .. py:method:: set_trace(frame=None) -> <Unknown>
      

      Start debugging from frame.

      If frame is not specified, debugging starts from caller's frame.



   .. py:attribute:: running
      :value: False