artemciy@gmail.com wrote:
--e89a8f3b55c652009c04cf6d24b9 Content-Type: text/plain; charset=ISO-8859-1
On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount quanah@zimbra.comwrote:
You can close the issue then, because I won't be producing one.
I don't understand why you would take the time to report a bug, but then refuse to provide the information necessary to fix it. That is not particularly helpful. :/
--Quanah
Quanah, from past experience I know that making a test case is a research endeavor that can be quite costly. IMO, refusing to investigate a bug without a test case is not a sane support politics.
Chasing "bugs" in 3rd party code that you haven't shared with us is not a sane policy. If we can't see the code, we certainly can't identify the root cause of the issue. Given that our library is working in our primary application (slapd) as well as multiple other projects, the burden of proof is on you to demonstrate that the bug is not caused by your C++ application.
For now I have found switching to Leveldb easier than taking another library for maintance (e.g. http://lambda-the-ultimate.org/node/4636 -> http://akkartik.name/blog/libraries). BTW, here is an example of good support: http://tracker.newdream.net/issues/3495