HandleExceptions

Bootstrap the given application.

Report PHP deprecations, or convert PHP errors to ErrorException instances.

Deprecations are handled here even when silenced with @. Other errors excluded by error_reporting() are passed on to PHP's standard handler so error_get_last() still reports them.

Report a deprecation to the "deprecations" logger.

Determine if deprecation errors should be ignored.

Ensure the "deprecations" logger is configured.

Ensure the "null" log driver is configured.

Handle an uncaught exception from the application.

Note: Most exceptions can be handled via the try / catch block in the HTTP and Console kernels. But, fatal error exceptions must be handled differently since they are not normal exceptions.

Render an exception to the console.

Handle the PHP shutdown event.

Create a new fatal error instance from an error array.

Forward a method call to the bootstrapper that currently owns the handlers.

A released error or exception handler can return to the top of PHP's stack when a handler installed after it is removed, so it forwards to the current owner. Shutdown callbacks only run for their own owner, since the owner's callback is registered too. Without an owner, errors fall back to PHP.

Determine if the error level is a deprecation.

Determine if the error type is fatal.

Get an instance of the exception handler.

Release the handlers installed for an application that is being discarded.

Restores the handlers, display_errors setting and application that were active before the application was bootstrapped, so later errors are reported without its flushed container. Handlers and settings changed by other code stay in place.

Flush all static state.

Flush the bootstrapper's global handlers state.