-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When debugging a core dump, there are a handful of warnings like
$ /opt/mongodbtoolchain/v5/bin/gdb ./bin/db_s_resharding_part2_test ./dump_db_s_resharding.322211.core ... Reading symbols from ./bin/db_s_resharding_part2_test... warning: .gdb_index address table has a range (0xbc93a - 0xbc93b) that overlaps with an earlier range, ignoring .gdb_index warning: core file may not match specified executable file. ... warning: .gdb_index address table has a range (0x7b937 - 0x7b938) that overlaps with an earlier range, ignoring .gdb_index warning: .gdb_index address table has a range (0x8dc2e - 0x8dc2f) that overlaps with an earlier range, ignoring .gdb_index warning: .gdb_index address table has a range (0x8a36d - 0x8a36e) that overlaps with an earlier range, ignoring .gdb_index
While these didn't obviously cause any function problems themselves, we should ensure they are innocent and consider silencing them. If they are a real problem, we should of course address their source.
Warnings introduced to gdb 17.1 here: https://gitlab.com/gnutools/binutils-gdb/-/commit/d40413bdfc32e87ca6d4436b164ee870811e6cc1
Original slack thread: https://mongodb.slack.com/archives/C07T35KELLC/p1770225609584869?thread_ts=1770223059.087099&cid=C07T35KELLC
- is related to
-
SERVER-120687 Use gdb from bazel for core analysis
-
- Backlog
-