envoyproxy / envoyproxy/envoy-mobile
signal handling: allow Envoy Logger to be ostream for signal handling
- Dominant language
- Java
- Stars
- 566
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
Currently Event::SignalAction installs std::cerr as the only ostream passed during signal handling on termination. For Envoy Mobile it would be far more useful to allow Envoy Logger to act as ostream so crash scopes could be output to platform-specific crash APIs.
Contributor guide
Research direction
Start by locating Event::SignalAction and tracing how std::cerr is installed as the termination-time ostream. Check how Envoy Logger could be exposed at that boundary for Envoy Mobile's platform-specific crash APIs. Done means crash scopes can be emitted through Envoy Logger during signal handling without losing the existing termination behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100