[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openldap-bugs
Subject:    [Issue 9037] observing crash in mdb_cursor_put()
From:       openldap-its () openldap ! org
Date:       2024-03-15 20:15:34
Message-ID: bug-9037-2-Xmr6L65su8 () http ! bugs ! openldap ! org/
[Download RAW message or body]

https://bugs.openldap.org/show_bug.cgi?id=9037

--- Comment #27 from mdufour@audiokinetic.com ---
We are also seeing rare instances of this crash since we released a version of
our product which uses LMDB. Specifically, call stack is:

mdb_cursor_put(MDB_cursor * mc, MDB_val * key, MDB_val * data, unsigned int
flags) Line 7998
mdb_put(MDB_txn * txn, unsigned int dbi, MDB_val * key, MDB_val * data,
unsigned int flags) Line 10107

where line 8183 is

nsize = IS_LEAF2(mc->mc_pg[mc->mc_top]) ? key->mv_size : mdb_leaf_size(env,
key, rdata);

and

mc->mc_top == 0
mc->mc_pg[0] == NULL
rc == -30798

Although we do not have a reproduction case, we do have a full crash dump with
heap of an unoptimized debug build of our application. There is no evidence of
stack corruption (in fact, mc->mc_pg[1] is still 0xcccccccccccccccc as per the
msvc run-time check initialization).

Unfortunately we do not have the matching LMDB file.

Anything we can provide to help narrow down the issue?

-- 
You are receiving this mail because:
You are on the CC list for the issue.=
[prev in list] [next in list] [prev in thread] [next in thread]