-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Storage 2017-05-29
I was trying to diagnose a hung wiredtiger-test-format-stress-sanitizer job on KodKod. I pointed GDB at the test format executable and it was able to get traces, but all of the variables were "optimized out". We need to work out why this happens specifically with wiredtiger-test-format-stress-sanitizer. I checked a wiredtiger-test-format-stress run at the same time on kodkod and it had the correct symbols, so it is likely something about the wiredtiger-test-format-stress-sanitizer job and potentially clang.
An example backtrace from a thread
Thread 14 (Thread 0x7fb9381e9700 (LWP 32219)): #0 0x00007fb9427e9a82 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00000000007a2599 in __wt_cond_wait_signal (session=<optimized out>, cond=<optimized out>, usecs=<optimized out>, run_func=<optimized out>, signalled=<optimized out>) at ../src/os_posix/os_mtx_cond.c:87 #2 0x0000000000a35009 in __wt_cond_wait (session=<optimized out>, cond=<optimized out>, usecs=<optimized out>, run_func=<optimized out>) at ../src/include/misc.i:19 #3 0x0000000000a3458f in __thread_run (arg=<optimized out>) at ../src/support/thread_group.c:29 #4 0x00007fb9427e5dc5 in start_thread () from /lib64/libpthread.so.0 #5 0x00007fb9419c973d in clone () from /lib64/libc.so.6