From artemciy@gmail.com Tue Nov 27 09:09:31 2012
From: artemciy@gmail.com
To: openldap-bugs@openldap.org
Subject: Re: (ITS#7448) "assertion failed" in MDB
Date: Tue, 27 Nov 2012 09:09:31 +0000
Message-ID: <201211270909.qAR99VD9068556@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4310196942736454665=="

--===============4310196942736454665==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

--047d7b2e40c6a4d17e04cf7665de
Content-Type: text/plain; charset=3DISO-8859-1

On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <hyc(a)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.

--047d7b2e40c6a4d17e04cf7665de
Content-Type: text/html; charset=3DISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <span dir=3D3D"ltr">&lt;<a href=3D
=3D3D"mailto:hyc(a)symas.com" target=3D3D"_blank">hyc(a)symas.com</a>&gt;</sp=
an> wr=3D
ote:<br><div class=3D3D"gmail_quote"><blockquote class=3D3D"gmail_quote" styl=
e=3D
=3D3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br></blockquote><blockquote class=3D3D"gmail_quote" style=3D3D"margin:0 0 0 =
.8=3D
ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class=3D3D"gmail_=
=3D
quote" style=3D3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
=3D
ex">
<div class=3D3D"im">Indeed, you might stress on <a href=3D3D"http://www.openl=
da=3D
p.org/its/index.cgi" target=3D3D"_blank">http://www.openldap.org/its/<u></u>i=
=3D
ndex.cgi</a> that bugs<br>
without a test case wouldn&#39;t be investigated so that people won&#39;t w=3D
aste<br>
their time.<br>
</div></blockquote>
<br>
<a href=3D3D"http://www.openldap.org/faq/data/cache/1122.html" target=3D3D"_b=
la=3D
nk">http://www.openldap.org/faq/<u></u>data/cache/1122.html</a></blockquote=3D
><div><br></div><div><span style=3D3D"font-family:&#39;Times New Roman&#39;;f=
=3D
ont-size:medium">&quot;In case the first aim doesn&#39;t succeed, and the p=3D
rogrammer=3DA0</span><em style=3D3D"font-family:&#39;Times New Roman&#39;;fon=
t-=3D
size:medium">can&#39;t</em><span style=3D3D"font-family:&#39;Times New Roman&=
=3D
#39;;font-size:medium">=3DA0see it failing themselves, the second aim of a bu=
=3D
g report is to describe what went wrong. Describe everything in detail. Sta=3D
te what you saw, and also state what you expected to see. Write down the er=3D
ror messages,=3DA0</span><em style=3D3D"font-family:&#39;Times New Roman&#39;=
;f=3D
ont-size:medium">especially</em><span style=3D3D"font-family:&#39;Times New R=
=3D
oman&#39;;font-size:medium">=3DA0if they have numbers in&quot;. -=3DA0</span>=
<f=3D
ont face=3D3D"Times New Roman" size=3D3D"3"><a href=3D3D"http://www.chiark.gr=
eene=3D
nd.org.uk/~sgtatham/bugs.html">http://www.chiark.greenend.org.uk/~sgtatham/=3D
bugs.html</a></font></div>
<div><br></div><div><font face=3D3D"Times New Roman" size=3D3D"3">Stack trace=
 a=3D
nd proposal to do ltrace is the best detail you&#39;ve got in a normal bug =3D
report.</font></div><div><font face=3D3D"Times New Roman" size=3D3D"3">Good l=
uc=3D
k.</font></div>
</div>

--047d7b2e40c6a4d17e04cf7665de--



--===============4310196942736454665==--