When an abort test fails in evergreen and it tries to put print the stack traces into the log it is using the wrong core file. The abort tests use parent/child processes. The child process runs "in" the database directory and the parent process runs "in" the directory above the database.

When the child process aborts unexpectedly, its core file ends up in, for example, WT_HOME/core.... The parent process has a signal handler, sig_handler that traps the SIGCHLD signal and the parent process also then exits/aborts. Doing that puts a core file from the parent in the directory above the home directory.

The evergreen jobs are using the core file from the parent and putting a not-useful stack in the logs. The stack dumping scripts/code should recognize the subset of tasks that are the abort tests and look for and use the correct, child-process core file for the stack dump.