[SERVER-56166] Have hang analyzer write per-process gdb files Created: 19/Apr/21  Updated: 29/Oct/23  Resolved: 14/Jun/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Mikhail Shchatko
Resolution: Fixed Votes: 2
Labels: dp-qp-stakeholder-request-2021-04, dp-qp-stakeholder-request-2021-07, tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: STM 2021-06-28
Participants:
Story Points: 1

 Description   

Prior to the work done in PM-1569, the hang analyzer would write separate debugger_mongod_<pid>.log files. This made it easy to search the thread stacks, etc. for a single process at a time. Now all of the gdb output across all mongod processes end up in a single debugger_mongod.log file and so cmd+f can jump between processes.

We should restore the old behavior of writing separate files with the `set logging file` command in gdb.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 16/Jun/21 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-56166 Have hang analyzer write per-process gdb files
Branch: SERVER-34632
https://github.com/mongodb/mongo/commit/a2ef55883402fa1a4e8f13d0cc0437fe9755cad1

Comment by Githook User [ 14/Jun/21 ]

Author:

{'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}

Message: SERVER-56166 Have hang analyzer write per-process gdb files
Branch: master
https://github.com/mongodb/mongo/commit/a2ef55883402fa1a4e8f13d0cc0437fe9755cad1

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