-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Build
-
Server Development Platform
-
Fully Compatible
-
ALL
-
-
0
Calls to gdb.lookup_type when using gdb are ubiquitous. Perhaps most notably is when pretty printing strings.
Running gdb on a dynamically linked mongo program is struggling mightily compared to a statically linked program with the following invocations:
- gdb.lookup_type("std::__cxx11::string")
- gdb.lookup_type("std::__cxx11::wstring")
On a mongo shell, the former call took maybe a minute? (pegs a single CPU) and consumed ~6-7GB of memory before succeeding. A follow-up call succeeded immediately (I assume the result was cached by gdb).
However when examining mongod on a spawn host, the lookup consumes all of the system memory and OOMs the gdb program before it gets a chance to succeed.
- duplicates
-
SERVER-71211 gdb-index causing bugs in server gdb
- Closed
- is related to
-
SERVER-50537 Create alternative gdb string pretty printer.
- Open
-
SERVER-71098 Create additional gdb tests
- Backlog
-
SERVER-70839 Spawning dynamically linked mongod processes takes ~30 secs on EVG
- Closed