[SERVER-67126] Remove LOGV2 call from printStackTrace no-LOGV2 codepath Created: 08/Jun/22  Updated: 29/Oct/23  Resolved: 21/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.12, 6.0.2, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Gabriel Marks Assignee: Gabriel Marks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0, v5.0
Sprint: Security 2022-06-13, Security 2022-06-27
Participants:
Linked BF Score: 45

 Description   

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.



 Comments   
Comment by Githook User [ 17/Aug/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-67126 Don't invoke LOGV2 in printStackTrace(ostream)
Branch: v5.0
https://github.com/mongodb/mongo/commit/74ee1fee32b076124b9406187b1afcc9abe768c4

Comment by Githook User [ 21/Jun/22 ]

Author:

{'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}

Message: SERVER-67126 Don't invoke LOGV2 in printStackTrace(ostream)
Branch: master
https://github.com/mongodb/mongo/commit/571abb2dc6a19e7ceb7beaaf346ccbdd0d20284b

Generated at Thu Feb 08 06:07:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.