When wiredtiger_open is called with a configuration string that includes

verbose=[handleops] 

and no message handler is set up, then a recursive loop results and the stack is consumed. Here is a fragment of the traceback:

frame #11623: 0x00000001001475a4 test_handle_ops_verbose`__wt_fprintf(session=0x0000000100803200, fstr=0x0000000101810f58, fmt="%s\n") + 372 at os_fstream.i:70
frame #11624: 0x00000001001457c2 test_handle_ops_verbose`__handle_message_default(handler=0x000000010017d5c8, wt_session=0x0000000100803200, message="[1472744200:562912][23674:0x7fff7505a000], connection: stdout: handle-printf") + 66 at err.c:44
frame #11625: 0x0000000100146198 test_handle_ops_verbose`__wt_eventv(session=0x0000000100803200, msg_event=true, error=0, file_name=0x0000000000000000, line_number=0, fmt="%s: handle-printf", ap=0x00007fff5fbfc0b0) + 2376 at err.c:299
frame #11626: 0x000000010014783d test_handle_ops_verbose`__wt_verbose(session=0x0000000100803200, flag=128, fmt="%s: handle-printf") + 413 at misc.i:62
frame #11627: 0x000000010014766b test_handle_ops_verbose`__wt_vfprintf(session=0x0000000100803200, fstr=0x0000000101810f58, fmt="%s\n", ap=0x00007fff5fbfc2b0) + 59 at os_fstream.i:52
frame #11628: 0x00000001001475a4 test_handle_ops_verbose`__wt_fprintf(session=0x0000000100803200, fstr=0x0000000101810f58, fmt="%s\n") + 372 at os_fstream.i:70
(repeating...)

If not having a message handler and using verbose=handleops is incompatible, we should return an error.