openldap-bugs

openldap-bugs@openldap.org

1 participants
21419 discussions

[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

[Issue 8502] mdb_cursor_count() == EINVAL for empty DB
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8502 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Howard Chu <hyc(a)openldap.org> --- Nothing worth changing here. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 8916] MDB_VL32 in readonly causes MDB_CORRUPTED
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=8916 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Howard Chu <hyc(a)openldap.org> --- The problem is that Windows doesn't let you use a readonly mapping that extends beyond the length of a file. This is noted in commit 5eb25c5cb9122fcc016e770bcc1f033e3a9d2a0f and 9d75a82ae10fdcee80b8b8e82c6ef9b6ab83dc47. Since the env is readonly we aren't expecting the file to grow. There's no provision for detecting that the underlying file is changing, in a readonly env. This is just a limitation of Windows so there's no workaround. Don't mix readonly envs with readwrite envs. -- You are receiving this mail because: You are on the CC list for the issue.

1 0

[Issue 7772] liblmdb sub-page growth when adding existing data
by openldap-its＠openldap.org 27 Apr '26

27 Apr '26

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

1 0

[Issue 7974] LDBM's "laggard reader" flaw still present, in continue of ITS#7904
by openldap-its＠openldap.org 26 Apr '26

26 Apr '26

https://bugs.openldap.org/show_bug.cgi?id=7974 Howard Chu <hyc(a)openldap.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #8 from Howard Chu <hyc(a)openldap.org> --- Fixing this implicitly inside LMDB is the wrong place. The calling app has to make the decision whether they can cope with breaking an atomic read txn into multiple pieces or not. Most applications that take a read txn expect it to stay atomic for the entire duration of their operation. Likewise, the calling apps are the only ones that can decide whether it's safe to kill any of their processes. -- 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