-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Test Format
-
1
-
ASeasonTooMany-2023-08-22
In this patch build, on top of the error mismatch, we can see the following:
[2023/05/11 13:57:33.732] Program terminated with signal SIGSEGV, Segmentation fault. [2023/05/11 13:57:33.732] #0 0x0000000000000000 in ?? () [2023/05/11 13:57:33.830] [Current thread is 1 (Thread 0xffff7a84c100 (LWP 23270))] [2023/05/11 13:57:33.830] #0 0x0000000000000000 in ?? () [2023/05/11 13:57:33.844] #1 0x000000000040c5d8 in wt_wrap_close_session (session=0x1c105148) at /data/mci/fcbcfe179fa64ae19ecf0a044dab2aae/wiredtiger/test/format/format_util.c:420 [2023/05/11 13:57:33.844] #2 0x000000000040ebe8 in ops_session_open (tinfo=tinfo@entry=0x1c93bc00) at /data/mci/fcbcfe179fa64ae19ecf0a044dab2aae/wiredtiger/test/format/ops.c:931 [2023/05/11 13:57:33.849] #3 0x0000000000413efc in ops (arg=0x1c93bc00) at /data/mci/fcbcfe179fa64ae19ecf0a044dab2aae/wiredtiger/test/format/ops.c:1027 [2023/05/11 13:57:33.850] #4 0x0000ffff8b5c2624 in start_thread (arg=0x413d50 <ops>) at pthread_create.c:477 [2023/05/11 13:57:33.850] #5 0x0000ffff8b4c949c in thread_start () at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78
The core indicates the following:
(gdb) p (WT_SESSION_IMPL*)(sap->trace)->close $4 = (WT_SESSION_IMPL *) 0x0
Looks like a test issue. Are we setting the session trace correctly?