[Date Prev][Date Next]
Re: (ITS#7448) "assertion failed" in MDB
Artem Grinblat wrote:
> On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <email@example.com
> <mailto:firstname.lastname@example.org>> 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.
> "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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/