| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Bool field of Terminated is new, as is the documentation:
data ProcessStatus
= Exited ExitCode -- ^ the process exited by calling
-- @exit()@ or returning from @main@
| Terminated Signal Bool -- ^ the process was terminated by a
-- signal, the @Bool@ is @True@ if a core
-- dump was produced
| Stopped Signal -- ^ the process was stopped by a signal
deriving (Eq, Ord, Show)
This is an API change, hence will need a major version bump.
|
| |
|
| |
|
|
|
|
| |
Fixes signals004(threaded1,threaded2) on OS X 32.
|
|
|
|
| |
I assume that this is what was intended.
|
| |
|
|
|
|
|
| |
We were freeing the string, but the string becomes part of the
environment.
|
|
|
|
| |
and remove code to support older versions
|
| |
|
|
|
|
|
| |
We now keep the HEAD version numbers as values which would be suitable
for immediate release.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes warnings following
commit 910a642294eb3547d0cbb3d5735ad81b964f137b
Author: Simon Peyton Jones <simonpj@microsoft.com>
Date: Mon Oct 29 23:25:25 2012 +0000
Do not treat a constructor in a *pattern* as a *use* of that constructor
I'm not sure if this is the right thing to do: In
commit 1c4608e3b8737dbb9204f850af4d680ccea7d8ec
Author: Simon Marlow <marlowsd@gmail.com>
Date: Thu Feb 19 10:05:32 2009 +0000
Rewrite of signal-handling.
the commit message says:
The new implementation has the capability to define signal handlers
that have access to the siginfo of the signal (#592), but this
functionality is not exposed in this patch.
but this at least gets validate builds working again, and we can change
it if necessary as part of #2451
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Paolo Capriotti <p.capriotti@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
sleep doesn't really work on GHC because it is always immediately
interrupted by SIGVTALRM used in the RTS.
I explained the problem in a comment and added a WARNING pragma.
usleep and nanosleep have a similar problem, but, since they have better
precision, they can be restarted, so they are not as unusable as sleep.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The other .Common modules aren't expose, and we think exposing this
one was a mistake.
|
| |
|
|
|
|
| |
They broken the build on OSX. See #2979.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Based on a patch from Arnaud Degroote <degroote@NetBSD.org> in
trac #5480.
|
|
|
|
| |
It may depend on getSlaveTerminalName if !defined(HAVE_OPENPTY)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new module System.Posix.ByteString provides exactly the same API
as System.Posix, except that:
- There is a new type: RawFilePath = ByteString
- All functions mentioning FilePath in the System.Posix API
use RawFilePath in the System.Posix.ByteString API
- RawFilePaths are not subject to Unicode locale encoding and
decoding, unlike FilePaths. They are the exact bytes passed to and
returned from the underlying POSIX API.
- Similarly for functions that deal in environment
strings (System.Posix.Env): these use untranslated ByteStrings
in System.Posix.Environment
- There is a new function
System.Posix.ByteString.getArgs :: [ByteString]
returning the raw untranslated arguments as passed to exec() when
the program was started.
|