[SERVER-37462] Archive core dumps on macOS hosts in Evergreen Created: 03/Oct/18  Updated: 29/Oct/23  Resolved: 13/Sep/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.3.1

Type: New Feature Priority: Minor - P4
Reporter: Benjamin Caimano (Inactive) Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: tig-hanganalyzer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-75033 Capture core dumps from test failures... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Security 2019-09-23
Participants:
Linked BF Score: 55

 Description   

See this task. Perhaps it got caught by the test infrastructure?



 Comments   
Comment by Githook User [ 13/Sep/19 ]

Author:

{'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-37462 Archive core dumps on macOS hosts in Evergreen
Branch: master
https://github.com/mongodb/mongo/commit/23239fdc63833126740f092e6a2f87586762a443

Comment by Andrew Morrow (Inactive) [ 05/Oct/18 ]

I think we should try turning it on for 4.1 where mmap is gone. Perhaps it will help us make sense of the DNS misbehavior we have seen on the platform.

Comment by Benjamin Caimano (Inactive) [ 03/Oct/18 ]

Huh, fascinating. Thanks for the context.

Comment by Max Hirschhorn [ 03/Oct/18 ]

ben.caimano, just for some historical context - core dumps weren't enabled on macOS because it lacks an equivalent to /proc/self/coredump_filter for filtering out memory-mapped files. They'd like be very large when running with the MMAPv1 storage engine and would need to see the state of things when running with the WiredTiger storage engine.

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