1. 24 Apr, 2007 1 commit
  2. 20 Apr, 2007 4 commits
  3. 19 Apr, 2007 5 commits
  4. 18 Apr, 2007 1 commit
  5. 19 Apr, 2007 2 commits
  6. 14 Apr, 2007 1 commit
  7. 18 Apr, 2007 9 commits
  8. 17 Apr, 2007 1 commit
    • Simon Marlow's avatar
      Re-working of the breakpoint support · cdce6477
      Simon Marlow authored
      This is the result of Bernie Pope's internship work at MSR Cambridge,
      with some subsequent improvements by me.  The main plan was to
       (a) Reduce the overhead for breakpoints, so we could enable 
           the feature by default without incurrent a significant penalty
       (b) Scatter more breakpoint sites throughout the code
      Currently we can set a breakpoint on almost any subexpression, and the
      overhead is around 1.5x slower than normal GHCi.  I hope to be able to
      get this down further and/or allow breakpoints to be turned off.
      This patch also fixes up :print following the recent changes to
      constructor info tables.  (most of the :print tests now pass)
      We now support single-stepping, which just enables all breakpoints.
        :step <expr>     executes <expr> with single-stepping turned on
        :step            single-steps from the current breakpoint
      The mechanism is quite different to the previous implementation.  We
      share code with the HPC (haskell program coverage) implementation now.
      The coverage pass annotates source code with "tick" locations which
      are tracked by the coverage tool.  In GHCi, each "tick" becomes a
      potential breakpoint location.
      Previously breakpoints were compiled into code that magically invoked
      a nested instance of GHCi.  Now, a breakpoint causes the current
      thread to block and control is returned to GHCi.
      See the wiki page for more details and the current ToDo list:
  9. 06 Apr, 2007 1 commit
  10. 04 Apr, 2007 2 commits
  11. 27 Mar, 2007 2 commits
    • Simon Marlow's avatar
      make GHCi use base:Prelude, not just Prelude · 4439532f
      Simon Marlow authored
      The module that GHCi uses for its default scope should be exactly
      base:Prelude, not whatever Prelude is found on the search path.
    • Simon Marlow's avatar
      more improvements for #1119 · 075a7bad
      Simon Marlow authored
      When GHCi compiles its code framgents for setting buffering, it wants
      to refer to base:System.IO rather than whatever System.IO is on the
      search path, unfortunately there's no way to do this in source code,
      so to hack around it we set the search path to empty before compiling
      these expressions (not forgetting to flush the finder cache
  12. 22 Mar, 2007 1 commit
  13. 08 Mar, 2007 2 commits
  14. 01 Mar, 2007 1 commit
  15. 27 Feb, 2007 2 commits
  16. 20 Feb, 2007 1 commit
    • bjpop@csse.unimelb.edu.au's avatar
      Constructor names in info tables · 7d6dffe5
      bjpop@csse.unimelb.edu.au authored
      This patch adds data constructor names into their info tables. 
      This is useful in the ghci debugger. It replaces the old scheme which
      was based on tracking data con names in the linker. 
  17. 21 Feb, 2007 3 commits
  18. 16 Feb, 2007 1 commit