[SERVER-44117] "processInfo" is sometimes omitted in stacktraces Created: 19/Oct/19  Updated: 29/Oct/23  Resolved: 28/Oct/19

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-11-04
Participants:
Linked BF Score: 0

 Description   

I had tried adding a printStackTrace call inside of unittest initialization, which resulted in the typical backtrace json object except it was missing the processInfo field which is necessary for mongosymb.py.

The theory was that printing a stacktrace requires a mongo initializer to run and this call to printStackTrace was happening prior to the necessary initialization.



 Comments   
Comment by Githook User [ 29/Oct/19 ]

Author:

{'name': 'Billy Donahue', 'username': 'BillyDonahue', 'email': 'billy.donahue@mongodb.com'}

Message: SERVER-44117 fix leak with local static
Branch: master
https://github.com/mongodb/mongo/commit/af1a00179bd00083fd6d4c3af34140e4ba2aac6d

Comment by Githook User [ 28/Oct/19 ]

Author:

{'username': 'BillyDonahue', 'email': 'billy.donahue@mongodb.com', 'name': 'Billy Donahue'}

Message: SERVER-44117 early stacktrace processInfo
Branch: master
https://github.com/mongodb/mongo/commit/4cd64d4068208811332845b4f02ffd83a08ad9ac

Comment by Billy Donahue [ 25/Oct/19 ]

Code Review http://mongodbcr.appspot.com/541840001

Generated at Thu Feb 08 05:05:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.