Changes between Version 48 and Version 49 of NewGhciDebugger


Ignore:
Timestamp:
Apr 9, 2007 3:22:31 PM (7 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewGhciDebugger

    v48 v49  
    211211 
    212212The following list describes issues where the debugger does not behave in the ideal way: 
    213  * Computations which fork concurrent threads can use breakpoints, but sometimes a thread gets blocked indefinitely. 
    214    Consider this program: 
    215    {{{ 
     213 * Computations which fork concurrent threads can use breakpoints, but sometimes a thread gets blocked indefinitely. Consider this program: 
     214{{{ 
    216215   main = do 
    217216      forkIO foo 
     
    221220 
    222221   bar = do something else 
    223    }}} 
    224    Suppose we have a breakpoint set somewhere inside the computation done by `foo`, but there are no breakpoints in the computation done by `bar`. When we run this program in GHCi the following things happen: 
     222}}} Suppose we have a breakpoint set somewhere inside the computation done by `foo`, but there are no breakpoints in the computation done by `bar`. When we run this program in GHCi the following things happen: 
    225223      * `foo` gets forked and `foo` and `bar` begin their work 
    226224      * `bar` completes its job and we return to the GHCi prompt (uh oh!) 
    227225      * `foo` eventually hits a breakpoint and attempts to return to the command line, but it can't because we are already there (in the previous step). 
    228  
    229    Now the foo thread is blocked, so we can't witness the breakpoint. 
     226Now the foo thread is blocked, so we can't witness the breakpoint. 
    230227 
    231228