1. 31 Aug, 2014 1 commit
  2. 10 Aug, 2014 1 commit
  3. 05 Aug, 2014 1 commit
    • Edward Z. Yang's avatar
      Filter out null bytes from trace, and warn accordingly, fixing #9395. · d360d440
      Edward Z. Yang authored
      
      
      Summary:
      Previously, if you ran trace "foo\0bar", the output was truncated so
      that everything after the null byte was omitted.  This was terrible.
      Now we filter out null bytes, and emit an extra trace saying that
      null bytes were filtered out.
      
      NB: we CANNOT fix debugBelch, because all printf variants *always*
      respect null bytes, even if you're using string precision such as
      %.*s.  The alternative would have been to introduce a new function
      debugRawBelch which did not use format strings and took an explicit
      string length, but I decided we generally should avoid putting null
      bytes in our trace messages, and warn the user.
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      
      Test Plan: validate
      
      Reviewers: hvr, austin
      
      Subscribers: simonmar, relrod, ezyang, carter
      
      Differential Revision: https://phabricator.haskell.org/D121
      
      GHC Trac Issues: #9395
      d360d440
  4. 04 Aug, 2014 1 commit
  5. 11 Jun, 2014 1 commit
  6. 28 May, 2014 1 commit
  7. 28 Apr, 2014 1 commit
  8. 14 Feb, 2014 2 commits
  9. 15 Nov, 2013 1 commit
    • Duncan Coutts's avatar
      Fix up test topHandler03 by ignoring unhelpful shell output · 14527c19
      Duncan Coutts authored
      Shells! Grrrr. Some shells print out a message if your program terminates with
      a signal. In the case of topHandler03 which deliberately exits with signal 15
      SIGTERM, some shells were printing "Terminated" to stdout.
      
      Why the testsuite driver goes via a shell I do not know (it also messes up the
      exit codes for signals).
      14527c19
  10. 14 Nov, 2013 1 commit
    • Duncan Coutts's avatar
      Add tests for the top level exception handler · 2ec9734d
      Duncan Coutts authored
      The top level exception handler is wrapped around main, and FFI exports.
      It handles exceptions that are not otherwise caught in user code. For
      most exception is just prints them, but handles a few specially,
      including ExitCode and UserInterrupt.
      
      On Unix it installs a signal handler for SIGINT to translate it into a
      UserInterrupt async exception.
      
      So we test that:
      
      1. receiving SIGINT does trigger a UserInterrupt async exception
      2. an unhandled UserInterrupt makes us kill ourselves with SIGINT
      3. an unhandled ExitFailure (-sig) makes us kill ourselves with sig
      2ec9734d
  11. 25 Oct, 2013 1 commit
  12. 08 Sep, 2013 2 commits
  13. 19 Jul, 2013 1 commit
  14. 08 Jun, 2013 1 commit
  15. 31 May, 2013 1 commit
  16. 15 May, 2013 1 commit
  17. 06 May, 2013 1 commit
    • AndreasVoellmy's avatar
      Update parallel IO manager to handle the invalid files in the same way as previous IO manager. · c5a4de9d
      AndreasVoellmy authored
      This patch affects the IO manager using kqueue. See issue #7773. If the kqueue backend cannot wait for events on a file, it will simply call the registered callback for the file immediately. This is the behavior of the previous IO manager. This is not ideal, but it is an initial step toward dealing with the problem properly. Ideally, we would use a non-kqueue mechanism for waiting on files (select seems most reliable) that cannot be waited on with kqueue.
      c5a4de9d
  18. 14 Feb, 2013 1 commit
  19. 12 Feb, 2013 1 commit
  20. 11 Feb, 2013 2 commits
  21. 08 Feb, 2013 1 commit
  22. 28 Jan, 2013 1 commit
  23. 25 Jan, 2013 1 commit
  24. 03 Jan, 2013 1 commit
  25. 13 Dec, 2012 2 commits
  26. 10 Dec, 2012 1 commit
    • Simon Marlow's avatar
      Add back new working QSem and QSemN implementations (#7417) · 2f32d1d2
      Simon Marlow authored
      We decided not to break existing users without providing an easy
      migration path.  For the time being I've made these implementations,
      which fix the bugs in the old versions and perform reasonably well.
      
      In due course we should move the concurrency functionality, including
      these modules, out of base and into a separate package.
      2f32d1d2
  27. 20 Jul, 2012 1 commit
  28. 02 Jul, 2012 1 commit
  29. 30 Mar, 2012 1 commit
  30. 23 Mar, 2012 1 commit
  31. 09 Mar, 2012 1 commit
  32. 01 Mar, 2012 3 commits
  33. 19 Nov, 2011 2 commits