--047d7b2e40c6a4d17e04cf7665de Content-Type: text/plain; charset=ISO-8859-1
On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu hyc@symas.com wrote:
Indeed, you might stress on http://www.openldap.org/its/**index.cgihttp://www.openldap.org/its/index.cgithat 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.htmlhttp://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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <span dir=3D"ltr"><<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc@symas.com</a>></span> wr= ote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8= ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_= quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1= ex"> <div class=3D"im">Indeed, you might stress on <a href=3D"http://www.openlda= p.org/its/index.cgi" target=3D"_blank">http://www.openldap.org/its/<u></u>i= ndex.cgi</a> that bugs<br> without a test case wouldn't be investigated so that people won't w= aste<br> their time.<br> </div></blockquote> <br> <a href=3D"http://www.openldap.org/faq/data/cache/1122.html" target=3D"_bla= nk">http://www.openldap.org/faq/<u></u>data/cache/1122.html</a></blockquote=
<div><br></div><div><span style=3D"font-family:'Times New Roman';f=
ont-size:medium">"In case the first aim doesn't succeed, and the p= rogrammer=A0</span><em style=3D"font-family:'Times New Roman';font-= size:medium">can't</em><span style=3D"font-family:'Times New Roman&= #39;;font-size:medium">=A0see it failing themselves, the second aim of a bu= g report is to describe what went wrong. Describe everything in detail. Sta= te what you saw, and also state what you expected to see. Write down the er= ror messages,=A0</span><em style=3D"font-family:'Times New Roman';f= ont-size:medium">especially</em><span style=3D"font-family:'Times New R= oman';font-size:medium">=A0if they have numbers in". -=A0</span><f= ont face=3D"Times New Roman" size=3D"3"><a href=3D"http://www.chiark.greene= nd.org.uk/~sgtatham/bugs.html">http://www.chiark.greenend.org.uk/~sgtatham/= bugs.html</a></font></div> <div><br></div><div><font face=3D"Times New Roman" size=3D"3">Stack trace a= nd proposal to do ltrace is the best detail you've got in a normal bug = report.</font></div><div><font face=3D"Times New Roman" size=3D"3">Good luc= k.</font></div> </div>
--047d7b2e40c6a4d17e04cf7665de--
-
artemciy＠gmail.com