You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have funcionality for dumping active sessions on crash, as part of issue #7300, but it isn't usable except through Envoy's signal handler: the session dump is only accessible via FatalErrorHandlerInterface, and Envoy::Event::DispatcherImpl won't register its fatal error handler unless Envoy is compiled with ENVOY_HANDLE_SIGNALS. I'd like to add an interface to call into the fatal error handlers from signal handlers other than Envoy's.
The text was updated successfully, but these errors were encountered:
…nal handlers (#12062)
Add hooks for calling fatal error handlers from non-Envoy signal handlers. Move register/removeFatalErrorHandler from SignalAction into a new FatalErrorHandler namespace, and add a new function, callFatalErrorHandlers, which runs the registered error handlers. This makes the crash logging from issue #7300 available for builds that don't use ENVOY_HANDLE_SIGNALS, as long as they do use ENVOY_OBJECT_TRACE_ON_DUMP.
Risk Level: Low
Testing: bazel test //test/...
Docs Changes: N/A
Release Notes: Added
Fixes#11984
Signed-off-by: Michael Behr <[email protected]>
We have funcionality for dumping active sessions on crash, as part of issue #7300, but it isn't usable except through Envoy's signal handler: the session dump is only accessible via FatalErrorHandlerInterface, and Envoy::Event::DispatcherImpl won't register its fatal error handler unless Envoy is compiled with ENVOY_HANDLE_SIGNALS. I'd like to add an interface to call into the fatal error handlers from signal handlers other than Envoy's.
The text was updated successfully, but these errors were encountered: