It might be possible that even though RKV was built in debug mode,
backing sys crate isn't building LMDB itself this way. On a very first
glance it looks like this is the case, always going for opt level 2:
I'll have a closer look at the build process and see what's going on.
Can you share your build process that resulted in LMDB debug functions
being optimized away? Did you build using the fuzzer via `cargo afl`?
I deleted the lmdb-rkv-sys-* directories from target/debug/build, edited
and added #define MDB_DEBUG 3 at the top of the file, then reran the cargo build
RUSTFLAGS="-Clink-arg=-fuse-ld=gold" cargo afl build -v
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/