This ticket came out of
WT-10789, the problem is that a variable was unfortunately optimized out. Evergreen defaults to running with -0g optimization level. From the manual page:
In a summary it is still possible that -Og can optimize out variables and is not guarrantee for developers to make sure that a particular variable will not be optimized. Setting the level to --O0 will fix this issue, which will be helpful in case
WT-10789 repros again.
Definition of Done
The aim of this ticket is to change the evergreen task to use -O0 instead.