[SERVER-69633] Spike: Investigate v4 debugging workflow issues Created: 13/Sep/22  Updated: 24/Oct/22  Resolved: 10/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Daniel Moody Assignee: Daniel Moody
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Gantt Dependency
has to be done before SERVER-62995 Update pretty printers as needed to w... Closed
Participants:

 Description   

There are several areas around pretty printers and debugging in general we want to investigate:

  1. unique pointers are broken in gcc 11.2 (currently deployed toolchain)
  2. std::set and static members sometimes is not printable when debugging with v4 gdb from v3/v4 compiled binaries
  3. Corefiles have bad source files from when using v4 gdb with v3/v4 compiled binaries
  4. The hang analyzer needs to be verified to be working with v4 gdb with v3/v4 compiled binaries.
  5. some gdb "hangs" on std::error_code/std::error_condition pretty printers:

I will write a detailed doc outlining my experiments and results.


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