Properly initialize all fields in CrashReporterCleanupContext.  This caused the buildbot failure earlier.

llvm-svn: 128071

Temporarily stop recovering resources in CrashRecoveryContext while I investigate further why this works on my machine and not on others.

llvm-svn: 128065

Provide a means for CrashRecovery clients to determine if code is currently running while crash recovery cleanups are being processed.

llvm-svn: 128008

Tweak CrashRecoveryContextCleanup to provide an easy method for clients to select between 'delete' and 'destructor' cleanups, and allow the destructor of CrashRecoveryContextCleanupRegister to be pseudo re-entrant.

llvm-svn: 127929

Tweak CrashRecoveryContext::GetCurrent() to return quickly if 'gCrsahRecoveryEnabled' is false.  This avoids us needing to go to thread local storage for
the performance sensitive case where we are compiling code.

llvm-svn: 127928

Augment CrashRecoveryContext to have registered "cleanup" objects that can be used to release resources during a crash.

llvm-svn: 127849

llvm-svn: 120298

llvm-svn: 118272

routine is off the stack. Otherwise we show up rather confusingly in the stack
trace.

llvm-svn: 116755

CrashRecovery: Clear the current context on the first crash, to avoid re-entering it if the cleanup code crashes.

llvm-svn: 111309

CrashRecovery: Add CrashRecoveryContext::GetCurrent(), so clients can find the active context from anywhere.

llvm-svn: 111308

llvm-svn: 111307

llvm-svn: 109872

llvm-svn: 109752

llvm-svn: 109721

 - This works, but won't handle crashes on stack overflow, or signals delivered
   to a thread other than the one that crashed. The latter is particular annoying
   on Darwin, because SIGABRT tends to go to the main thread.

llvm-svn: 109717

 - Designed as a simple wrapper to allow clients to attempt to catch crashes
   (memory errors, assertion violations, etc.) and do some kind of recovery.

 - Currently doesn't actually attempt to catch crashes.

llvm-svn: 109586