Klaus Malorny wrote:
Hi,
I am using version 0.9.20 on Linux (Ubuntu derivates, uname see [1], [2]).
Version 0.9.20 was never officially released. The release was withdrawn due to a corruption bug. I suggest you downgrade to 0.9.19.
On 3/20/17 3:32 PM, Howard Chu wrote:
Klaus Malorny wrote:
Hi,
I am using version 0.9.20 on Linux (Ubuntu derivates, uname see [1], [2]).
Version 0.9.20 was never officially released. The release was withdrawn due to a corruption bug. I suggest you downgrade to 0.9.19.
Hi,
after hitting a known problem with 0.9.18, I went to the Git repository to fetch the latest release I found there -- this is why I took 0.9.20.
I have repeated my test with 0.9.19, but unfortunately, the very same error occurred...
I am going to try to write a small C program to see whether I can reproduce the behaviour.
Regards,
Klaus
On 3/21/17 2:01 PM, Klaus Malorny wrote:
On 3/20/17 3:32 PM, Howard Chu wrote:
Klaus Malorny wrote:
Hi,
I am using version 0.9.20 on Linux (Ubuntu derivates, uname see [1], [2]).
Version 0.9.20 was never officially released. The release was withdrawn due to a corruption bug. I suggest you downgrade to 0.9.19.
Hi,
after hitting a known problem with 0.9.18, I went to the Git repository to fetch the latest release I found there -- this is why I took 0.9.20.
I have repeated my test with 0.9.19, but unfortunately, the very same error occurred...
I am going to try to write a small C program to see whether I can reproduce the behaviour.
Regards,
Klaus
Hi,
I am now able to reproduce the problem with a sample program. I guess that the problem is somewhat deeper and not necessarily directly related to mdb_cursor_del as it seems to depend on the order the data is inserted into the database. If I do this in a pre-ordered way, the problem does not occur, but if I shuffle the data, it does. I also tried a smaller number of records, but then the problem disappears also.
I have attached the test program to this e-mail. I hope it does not get filtered out.
Regards,
Klaus
Thanks. I've filed ITS#8622 with this and expanded a bit on it.
openldap-technical@openldap.org