Yep, linking against BerkeleyDB 3.1 was causing the segmentation fault. Problem solved. Please close this issue at your convenience.