-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Developer Productivity
-
3
-
StorEng - Defined Pipeline
GDB seems to have trouble locating the correct source files from a coredump after compiling with GCC 11.2 in the v4 mongodbtoolchain. I came across this issue after reproducing a test/format failure locally. Using clang in the v4 toolchain provides a sufficient workaround for compiling tests locally. However, the concern I have here is that we may have the same trouble from a dropped core if a test in evergreen compiles with the above GCC. We should investigate this further to confirm if this is a concern in evergreen and provide a fix.
I've added an assert in __wt_txn_commit as an example:
#3 0x00007feb94758378 in __wt_txn_commit (session=0x7feb94a0f010, cfg=0x0) at /home/ubuntu/wiredtiger/build/time_inline.h:1530 1530 /home/ubuntu/wiredtiger/build/time_inline.h: No such file or directory. (gdb) l 1525 in /home/ubuntu/wiredtiger/build/time_inline.h