The system API's will be shifted over to returning an error_code, and returning
other return values as out parameters to the function.

Code that needs to check error conditions will use the errc enum values which
are the same as the posix_errno defines (EBADF, E2BIG, etc...), and are
compatable with the error codes in WinError.h due to some magic in system_error.

An example would be:

if (error_code ec = KillEvil("Java")) { // error_code can be converted to bool.
  handle_error(ec);
}

llvm-svn: 119360

llvm-svn: 118367

llvm-svn: 118128

llvm-svn: 118127

limits on their own.

llvm-svn: 118113

llvm-svn: 118110

llvm-svn: 118106

llvm-svn: 118105

llvm-svn: 118102

llvm-svn: 118096

Additionally, move the implementation of appendSuffix to Path.cpp: it is
platform-independent.

llvm-svn: 118089

llvm-svn: 118086

llvm-svn: 118058

This makes its behaviour more consistent across platforms.

llvm-svn: 118048

llvm-svn: 118042

llvm-svn: 117666

being not found from the file being not executable. 

llvm-svn: 117664

executing the child process and abnormal child process termination.

llvm-svn: 117661

which contains slashes is inconsistent with the meaning of PATH on
Unix-type platforms, and pretty surprising.

If the user has given a specific path to execute and we can't
execute it, we should fail and say why.  (Apparently the new
posix_spawn code doesn't always say why, but that's a separate
issue.)

llvm-svn: 117596

Original commit message:

    On "Unix", if Program::FindProgramByName is given a name containing
    slashes, just go with it, regardless of whether it looks like it will
    be executable. This follows the behavior of sh(1) more closely.

It's better when behaviour is consistent between platforms. This change also
makes FindExecutable() behave as expected on unix-likes (before this commit, it
used to always succeed).

llvm-svn: 117582

llvm-svn: 117581

llvm-svn: 116072

llvm-svn: 115991

false positive, at least on Darwin. I haven't filed this, but you can feel free.

llvm-svn: 115242

end up altering the thread on which crashes are done because of its use of
Darwin's broken raise() implementation.

llvm-svn: 114558

GetMainExecutable yet.

llvm-svn: 113240

Minix apparently doesn't like double-slash separators, and there's
no apparent need for them here.

llvm-svn: 112844

llvm-svn: 112705

llvm-svn: 112662

of the current thread. This has the unfortunate effect that assert() and abort()
will end up bypassing our crash recovery attempts. We work around this for
anything in the same linkage unit by just defining our own versions of the
assert handler and abort.

llvm-svn: 111583

llvm-svn: 110183

llvm-svn: 109686

just use memset to zero the entire struct.

llvm-svn: 108330

patch by Lasse Kärkkäinen in PR7404.

llvm-svn: 108110

llvm-svn: 107785

and change llvm::sys::RunInterruptHandlers to call that function directly
instead of calling SignalHandler, because the rest of SignalHandler
invokes side effects which aren't appropriate, including raising the
signal.

llvm-svn: 104896

can't be read, since it isn't cleared on other error paths.

llvm-svn: 104852

stuff.

llvm-svn: 103333

llvm-svn: 101790

llvm-svn: 101785