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

--- Comment #8 from bdallen@nps.edu bdallen@nps.edu --- Hi Howard,

Please forgive me.  Yes, I started this ten years ago on another project which was resolved.  When I saw your new post https://bugs.openldap.org/show_bug.cgi?id=8394#c3 I assumed they were related.  They are not.

Good to hear you are still supporting LMDB.  It worked very well for me.

Cheers, -Bruce

On 4/28/26 10:03, openldap-its@openldap.org wrote:

NPS WARNING: *external sender* verify before acting.

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

--- Comment #7 from Howard Chu hyc@openldap.org --- (In reply to bdallen@nps.edu from comment #6)

...

Hi Howard,

I did not submit issue 8394. I suspect somebody in Pico Technical Support Team submitted this in my name in response to SUPPORT-63913 Crashing bug in pypicosdk that I submitted to support@picotech.com. I responded to you incorrectly believing I was working with Pico Technical Support.

Meanwhile, I can offer some information:

1. You cannot reproduce this bug without having a PicoScope connected to

a USB port and without "sudo apt install picoscope" per https://www.picotech.com/downloads/linux and without "pip install pypicosdk". 2) I would suspect the core dump reported is the result of object mismanagement in Python bindings in pypicosdk except that someone in Pico Technical Support has stated the fault is line 6590 of mdb.c.

Please let me know if I can help.

Regards, -Bruce

Thanks for the information. That initial report is from 10 years ago, and LMDB v0.9.18 is long since obsolete.

We're about to release v1.0.0. It would probably be worth seeing if you can reproduce the problem with that release candidate. https://git.openldap.org/openldap/openldap/-/tree/mdb.RE/1.0?ref_type=heads

For what it's worth, using clang-20's -fsanitize=type sanitizer, it shows some potential problems in v0.9.18 but it only gives false positives with the 1.0 branch.

-- You are receiving this mail because: You reported the issue.