[SERVER-50537] Create alternative gdb string pretty printer. Created: 25/Aug/20  Updated: 25/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-50476 gdb.lookup_type on dynamically linked... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

Dynamic builds being the default in our testing has left us in the unfortunate position that barring some investigation and insight, coredumps can no longer be freely inspected. The standard pretty printers that get installed for (certain) strings will peg the CPU and consume all the memory when inspecting a mongod process.

The problematic invocation is gdb.lookup_type for std::_cxx11::string and std::_cxx11::wstring.

The ideal outcome of this ticket is two-fold:

  • Create a custom pretty printer for std::string objects that avoid calling gdb.lookup_type on the aforementioned problematic types.
  • Create a (literal) patch snippet that can be applied to the mongodb toolchain libstdcxx/v6/printers.py file which disables the problematic printers registered here. Add this snippet into buildscripts/setup_spawnhost_coredump.


 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

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