openldap-bugs

openldap-bugs@openldap.org

1 participants
21422 discussions

[Issue 8386] Small LMDB Documentation patch
by openldap-its＠openldap.org 06 May '26

06 May '26

https://bugs.openldap.org/show_bug.cgi?id=8386 --- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> --- mdb/RE0.9: • 9a647381 by Philipp Storz at 2026-04-15T17:32:58+01:00 ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc mdb.master: • 7b5ffe1b by Philipp Storz at 2026-04-15T17:32:14+01:00 ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc mdb.master3: • 06680017 by Philipp Storz at 2026-04-15T17:33:05+01:00 ITS#8386 lmdb: be a bit more precise that mdb_get retrieves data in intro.doc -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9011] add mdb_txn_flags()
by openldap-its＠openldap.org 04 May '26

04 May '26

https://bugs.openldap.org/show_bug.cgi?id=9011 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Howard Chu <hyc(a)openldap.org> --- Added to git mdb.master3, mdb.RE/1.0 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 9011] add mdb_txn_flags()
by openldap-its＠openldap.org 03 May '26

03 May '26

https://bugs.openldap.org/show_bug.cgi?id=9011 --- Comment #4 from code(a)doriantaylor.com --- I was trying to determine why I got a notification for this bug, and I see now that it was because I filed a later one which was marked duplicate. Indeed, my remarks on issue 9188 constitute why a language binding would need to know if a transaction was read-only. In the Ruby bindings for LMDB which I now maintain, it's easy to find situations like db.transaction(true, &proc) # `true` enables read-only ...where `proc` itself does another transaction. I have semi-fixed this so read-only transactions "nest" by making the call a no-op if a transaction is already active, but it's still possible for read-write transactions to find their way inside read-only ones. So being able to create a `txn.readonly?` predicate would be useful for programmers downstream to better orient themselves. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8394] LMDB fails GCC5 without -fno-strict-aliasing
by openldap-its＠openldap.org 29 Apr '26

29 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8394 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|SUSPENDED |WORKSFORME -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8394] LMDB fails GCC5 without -fno-strict-aliasing
by openldap-its＠openldap.org 28 Apr '26

28 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8394 --- Comment #8 from bdallen(a)nps.edu <bdallen(a)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(a)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(a)openldap.org> --- > (In reply to bdallen(a)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(a)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. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8394] LMDB fails GCC5 without -fno-strict-aliasing
by openldap-its＠openldap.org 28 Apr '26

28 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8394 --- Comment #7 from Howard Chu <hyc(a)openldap.org> --- (In reply to bdallen(a)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(a)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 are on the CC list for the issue.

1 0

[Issue 8394] LMDB fails GCC5 without -fno-strict-aliasing
by openldap-its＠openldap.org 28 Apr '26

28 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8394 --- Comment #6 from bdallen(a)nps.edu <bdallen(a)nps.edu> --- 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(a)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 -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8394] LMDB fails GCC5 without -fno-strict-aliasing
by openldap-its＠openldap.org 28 Apr '26

28 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8394 --- Comment #5 from Howard Chu <hyc(a)openldap.org> --- (In reply to bdallen(a)nps.edu from comment #4) > Here is the code I used which generates the core dump in round 2. It > should complete 10 rounds then say "Done.": > > import pypicosdk as psdk > > def test(n): > print(n, "checkpoint.a") > scope = psdk.psospa() > print(n, "checkpoint.b") > scope.open_unit() > print(n, "checkpoint.c") > scope.close_unit() > print(n, "checkpoint.d") > > if __name__ == "__main__": > for i in range(1, 11): > test(i) > print("Done.") > > I have no idea how to install pypicosdk. You're going to have to provide sufficient info for someone to actually reproduce the software you're running. What I see here https://github.com/picotech/pyPicoSDK " Go to PicoTech downloads picotech.com/downloads Find your PicoScope in the list and click through Download and install PicoSDK for your operating system " Since I have no PicoScope I have no idea what to install. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8335] MDB_MULTIPLE issues
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8335 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |TEST --- Comment #8 from Howard Chu <hyc(a)openldap.org> --- Fixed in git -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8335] MDB_MULTIPLE issues
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8335 --- Comment #7 from Howard Chu <hyc(a)openldap.org> --- Bryan Matsuo's post, for reference https://lists.openldap.org/hyperkitty/list/openldap-technical@openldap.org/… -- You are receiving this mail because: You are on the CC list for the issue.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs