Artem Grinblat wrote:

On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:

    Indeed, you might stress on http://www.openldap.org/its/__index.cgi
    <http://www.openldap.org/its/index.cgi> that bugs
    without a test case wouldn't be investigated so that people won't waste
    their time.


http://www.openldap.org/faq/__data/cache/1122.html
<http://www.openldap.org/faq/data/cache/1122.html>

"In case the first aim doesn't succeed, and the programmer /can't/ see it failing themselves, the second aim of a bug report is to describe what went wrong. Describe everything in detail. State what you saw, and also state what you expected to see. Write down the error messages, /especially/ if they have numbers in". - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Stack trace and proposal to do ltrace is the best detail you've got in a normal bug report. Good luck.

A complete stack trace is usually sufficient, when we have complete source code in hand. In this case your source code is not present.

Ultimately the question is "do you want help to make this work?" Clearly you're not interested in helping. ITS closed.