Michael, it looks like wiredtiger_open isn't handling the "logging" configuration word (I'm trying to run bt with the -l argument).
Not sure what's going wrong, but "logging" is getting passed in the config argument to wiredtiger_open, but then (and this is where I start guessing), the search routine is searching the default config list, and not the top-level config list, and the default config list contains "logging=false".
Just a suggestion, maybe logging should take a file name argument ("logging=mylogfile") so apps can re-direct the logging information where they want it?
Or maybe it's a callback, do apps want to punch this stuff into a stream somehow?
- is related to
WT-47 segfault in automated testing