@agorrod: wtperf core dumps if report_interval is set to 0 (I was trying to turn reports off).
(gdb) where
#0 0x0000000000404250 in execute_populate (cfg=0x7fffffffd850)
at ../../../bench/wtperf/wtperf.c:686
WT-1 0x000000000040522c in main (argc=5, argv=0x7fffffffd9a8)
at ../../../bench/wtperf/wtperf.c:1043
(gdb) frame 0
#0 0x0000000000404250 in execute_populate (cfg=0x7fffffffd850)
at ../../../bench/wtperf/wtperf.c:686
686 if (elapsed % 100 == 0 &&
(gdb) l
681 * Sleep for 100th of a second, report_interval is in second
682 * granularity, so adjust accordingly.
683 */
684 usleep(10000);
685 elapsed += 1;
686 if (elapsed % 100 == 0 &&
687 (elapsed / 100) % cfg->report_interval == 0) {
688 lprintf(cfg, 0, 1, "%" PRIu64 " ops in %d secs",
689 g_npop_ops - last_ops, cfg->report_interval);
690 last_ops = g_npop_ops;
(gdb) p cfg->report_interval
$4 = 0
I'm not sure if turning off reports in wtperf is OK or not, so I'm going to leave this one for someone else.
- related to
-
WT-1 placeholder WT-1
- Closed