When printing a stack trace to somewhere other than the logging subsystem, we should maintain the invariant that we will not invoke the logging subsystem. This can cause issues for the synchronous signal handler.
Remove LOGV2 call from printStackTrace no-LOGV2 codepath
- Assignee:
-
Gabriel Marks
- Reporter:
-
Gabriel Marks
- Votes:
-
0 Vote for this issue - Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: