0 Replies Latest reply: Aug 3, 2014 8:11 AM by compmaniak RSS

    Berkeley DB 6.1.19 crashes while opening damaged environment with DB_FAILCHK flag. Is it a bug?




      After migrating to 6.1.19 release I found the case when Berkeley crashes attempting to open environment with dead processes in it. I've published MSVC2010 solution (failchk_crush) and damaged environment (example) in my dropbox https://www.dropbox.com/sh/wmx9c48y373gobm/AAC53UnSY_olSGpM4nwAWNSha

      'failchk_crush' solution contains statically built berkeley library ( with Unicode support and /Z7 /MDd flags ). To reproduce a program crash you should copy all contents of 'example' folder into 'failchk_crush/test' folder and run a solution.

      A first run crashes and prints this:

      BDB0113 Thread/process 9688/2344002002 failed: BDB1507 Thread died in Berkeley DB library

      __env_in_api: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

      A next run doesn't crash and prints this:

      BDB0060 PANIC: fatal region error detected; run recovery

      DbEnv::open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery

      6.0.30 release handles this case well. Please, take a look at this issue and let me know if it's a bug.