The email Sue & have been exchanging was about a core dump in wtperf, with the shared-cache-stress.wtperf runner.
I've been running that runner locally on a couple of machines, and I've seen one core dump. Here's the stack:
(gdb) where #0 0x0000000801ac0bdb in strlen () from /lib/libc.so.7 WT-1 0x00000000004a6009 in __wt_config_subgets (session=0x80651e080, cfg=0x7ffff1f8fd70, key=0x635f646572616873 <Address 0x635f646572616873 out of bounds>, value=0x7ffff1f8fd50) at src/config/config.c:742 WT-2 0x000000000040dbe6 in wiredtiger_open ( home=0x80301b300 "/tmp/WT_TEST/D22", event_handler=0x0, config=0x803026920 "create,statistics=(none),shared_cache=(name=wt-cache,size=536870912,reserve=10MB,chunk=20MB,)", wt_connp=0x80302e528) at src/conn/conn_api.c:1352 WT-3 0x0000000000409207 in close_reopen (cfg=0x80302e500) at wtperf.c:1352 WT-4 0x000000000040780b in start_run (cfg=0x80302e500) at wtperf.c:1801 WT-5 0x0000000000407e2d in thread_run_wtperf (arg=0x80302e500) at wtperf.c:1735 WT-6 0x00000008011474a4 in pthread_create () from /lib/libthr.so.3 WT-7 0x0000000000000000 in ?? () (gdb) frame 2 WT-2 0x000000000040dbe6 in wiredtiger_open ( home=0x80301b300 "/tmp/WT_TEST/D22", event_handler=0x0, config=0x803026920 "create,statistics=(none),shared_cache=(name=wt-cache,size=536870912,reserve=10MB,chunk=20MB,)", wt_connp=0x80302e528) at src/conn/conn_api.c:1352 1352 ret = __wt_config_subgets(session, &cval, ft->name, &sval); Current language: auto; currently minimal (gdb) p *ft $1 = {name = 0x0, flag = 0} (gdb) down WT-1 0x00000000004a6009 in __wt_config_subgets (session=0x80651e080, cfg=0x7ffff1f8fd70, key=0x635f646572616873 <Address 0x635f646572616873 out of bounds>, value=0x7ffff1f8fd50) at src/config/config.c:742 742 { key, strlen(key), 0, WT_CONFIG_ITEM_STRING }; (gdb) p key $2 = 0x635f646572616873 <Address 0x635f646572616873 out of bounds> (gdb) printf "%s\n", &key shared_cp????
Maybe the stack got overwritten?
I've been running under valgrind, but no joy so far.
@sueloverso, @agorrod: I've kept the core, if anybody has ideas on things to look at.
- is related to
-
WT-1243 Fix a bug in configuration parsing for lists.
- Closed
- related to
-
WT-1 placeholder WT-1
- Closed
-
WT-2 What does metadata look like?
- Closed
-
WT-3 What file formats are required?
- Closed
-
WT-4 Flexible cursor traversals
- Closed
-
WT-5 How does pget work: is it necessary?
- Closed
-
WT-6 Complex schema example
- Closed
-
WT-7 Do we need the handle->err/errx methods?
- Closed