https://bugs.openldap.org/show_bug.cgi?id=9297
Howard Chu hyc@openldap.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Howard Chu hyc@openldap.org --- (In reply to Konstantin Andreev from comment #4)
(In reply to Howard Chu from comment #3)
So again I repeat myself - what other return codes do you see?
What you are asking for is a proof that defect hits the leak.
So I should investigate LMDB sources, develop the test that causes mdb_cursor_get() to return something other than 0 or MDB_NOTFOUND, and, finally, to trigger a leak in mdb_add/mdb_search <-> mdb_dn2entry interaction.
Given that you have officially documented that mdb_cursor_get() returns undocumented error conditions.
cursor_get may return EINVAL when given invalid parameters or for other misuses of its API. back-mdb never misuses the API. Therefore, your concern here is invalid.
Closing this.