1. 07 May, 2007 3 commits
  2. 06 May, 2007 1 commit
  3. 04 May, 2007 3 commits
  4. 03 May, 2007 3 commits
  5. 01 May, 2007 1 commit
    • chevalier@alum.wellesley.edu's avatar
      Remove references to -fticky-ticky flag · 3c506a6c
      chevalier@alum.wellesley.edu authored
      -ticky is the command-line flag for ticky-ticky profiling now, but
      internally, the -fticky-ticky flag was used to represent whether ticky
      was on. This led to link errors if the user supplied -fticky-ticky but
      not -ticky (ticky code would be generated but the wrong RTS library
      would be passed to the linker). I removed references to -fticky-ticky
      -- now, only the way flags dictate whether ticky is on, and
      -fticky-ticky is no longer accepted as a command-line option.
  6. 02 May, 2007 3 commits
    • simonpj@microsoft.com's avatar
      Import fiddling · c916244f
      simonpj@microsoft.com authored
    • Simon Marlow's avatar
      Refactoring, tidyup and improve layering · 86bec429
      Simon Marlow authored
      The stack of breakpoint resume contexts is now part of the
      InteractiveContext and managed by the GHC API.  This prevents misuse
      of the resume context by the client (e.g. resuming a breakpoint that
      isn't the topmost, which would lead to a confused IC at the least).
      I changed the TypeEnv in the IC to a [Id].  It only contained Ids
      anyway, and this allows us to have shadowing, which removes an ugly
      and annoying restriction.
      The parts of the GHC API which deal with interactive evaluation are
      now in a module of their own, InteractiveEval.
    • Simon Marlow's avatar
      Print the "skipping" messages at verbosity 2 again · e1f7582a
      Simon Marlow authored
      This was accidentally changed to 1 in the HEAD a while ago, the
      behaviour is now the same as 6.6.x again.
  7. 30 Apr, 2007 2 commits
  8. 29 Apr, 2007 1 commit
  9. 27 Apr, 2007 2 commits
  10. 26 Apr, 2007 4 commits
    • chevalier@alum.wellesley.edu's avatar
      Avoid segfault when ticky file argument is stderr · ed95d86d
      chevalier@alum.wellesley.edu authored
      If you compiled a program with -ticky and ran it with:
      ./foo +RTS -rstderr -RTS
      the result would be a segfault. This was because the RTS interprets stderr to
      mean "use debugBelch to print out messages," and sets the ticky file pointer
      to NULL as a result, but PrintTickyInfo (the function in Ticky.c that prints
      out the ticky report) wasn't checking for NULL.
      I changed PrintTickyInfo to check whether the ticky file pointer is NULL and 
      output to stderr if so.
      Also removed an unused import from CodeOutput.lhs.
    • Simon Marlow's avatar
      getRdrNamesInScope: return interactively-bound names too · cf997f80
      Simon Marlow authored
      so completion can now complete names of local bindings
    • Simon Marlow's avatar
      unused import · 095be20c
      Simon Marlow authored
    • Simon Marlow's avatar
      Give a better error message when we try to print a value of unknown type · 97351f5d
      Simon Marlow authored
        Stopped at ../Test3.hs:(1,0)-(2,30)
        _result :: [a]
        [../Test3.hs:(1,0)-(2,30)] *Main> _result
            Ambiguous type variable `a' in the constraint:
              `Show a' arising from a use of `print' at <interactive>:1:0-6
            Cannot resolve unkonwn runtime types: a
            Use :print or :force to determine these types
  11. 25 Apr, 2007 3 commits
  12. 24 Apr, 2007 4 commits
  13. 25 Apr, 2007 1 commit
  14. 22 Apr, 2007 1 commit
    • simonpj@microsoft.com's avatar
      Fixes to datacon wrappers for indexed data types · 70918cf4
      simonpj@microsoft.com authored
      nominolo@gmail.com pointed out (Trac #1204) that indexed data types
      aren't quite right. I investigated and found that the wrapper
      functions for indexed data types, generated in MkId, are really very
      confusing.  In particular, we'd like these combinations to work
      	newtype + indexed data type
      	GADT + indexted data type
      The wrapper situation gets a bit complicated!  
      I did a bit of refactoring, and improved matters, I think.  I am not
      certain that I have gotten it right yet, but I think it's better.
      I'm committing it now becuase it's been on my non-backed-up laptop for
      a month and I want to get it into the repo. I don't think I've broken
      anything, but I don't regard it as 'done'.
  15. 20 Apr, 2007 2 commits
  16. 19 Apr, 2007 2 commits
  17. 18 Apr, 2007 4 commits
    • Simon Marlow's avatar
      Restore the interactive context when resuming a breakpoint · 6645c011
      Simon Marlow authored
      So that we don't accumulate bindings from previous breakpoints, which
      could lead to a space leak.
    • Simon Marlow's avatar
      remove dead code · 0de47da8
      Simon Marlow authored
    • Simon Marlow's avatar
      Various cleanups and improvements to the breakpoint support · 38e7ac3f
      Simon Marlow authored
        - move parts of the debugger implementation below the GHC API where
          they belong.  There is still more in Debugger that violates the
          layering, hopefully I'll get to that later.
        - instead of returning an IO action from runStmt for resuming,
          return a ResumeHandle that is passed to GHC.resume.
        - breakpoints now return [Name] which is displayed in the same
          way as when a binding statement is executed.
        - :load, :add, :reload now clear the active breakpoints and context
        - :break gives a sensible error when used on a non-interpreted module
        - export breakpoint-related types from GHC
        - remove a bunch of layer-violating imports from InteractiveUI
        - remove some more vestiges of the old breakpoint code (topLevel in
          the GHCi state).
        - remove TickTree and use a simple array instead, cached per module
    • Simon Marlow's avatar
      add module header · 71f74505
      Simon Marlow authored