Changes between Version 67 and Version 68 of NewGhciDebugger


Ignore:
Timestamp:
Apr 9, 2007 6:43:20 PM (8 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NewGhciDebugger

    v67 v68  
    395395 
    396396In the debugger the process of evaluating an expression is made more intricate. The reason is that if the expression thread hits a breakpoint it will want to return ''early'' to the GHCi thread, so that the user can access the GHCi prompt, issue commands ''etcetera''.  
     397 
     398This raises a few questions: 
     399 * How do we arrange for the expression thread to stop and return early? 
     400 * What information needs to be passed from the expression thread to the GHCi thread, and how do we arrange that flow of information? 
     401 * How do we wake up the GHCi thread and return to the prompt? 
     402 * How do we continue execution of the expression thread after we have hit a break point? 
     403 * What happens if we are running in the GHCi thread after a breakpoint, and we evaluate some other expression which also hits a breakpoint (i.e. what about nested breakpoints?)