Details
-
Bug
-
Resolution: Gone away
-
Major - P3
-
None
-
None
-
ALL
-
Service arch 2020-07-13, Service Arch 2020-08-10, Service Arch 2020-08-24, Service arch 2020-09-07, Service arch 2020-09-21
-
16
Description
This is a follow-on ticket for SERVER-47775, which originally spotted the issue with using libunwind to collect stack trace, in particular on RHEL. This ticket should investigate the underlying cause and provide fixes. More information is available in linked tickets.
Attachments
Issue Links
- has to be done before
-
SERVER-48202 Test printStackTrace on initialization
-
- Backlog
-
- is related to
-
SERVER-47775 LOGV2_FATAL failed to print stack trace
-
- Closed
-