openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

Re: (ITS#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by jvcelak＠redhat.com 28 Nov '12

28 Nov '12

> > Not happening here: > Your patch is invalid, but it appears there was a bug in the underlying > back-ldif code. Still, it did not result in a SEGV. back-ldif is now fixed > in master. e1ccebcf indeed fixes the problem. (I can see the SEGV when started via gdb.) Thanks. Jan

1 0

(ITS#7453) Reset(MDB_NOSYNC/MDB_NOMETASYNC) fails
by h.b.furuseth＠usit.uio.no 27 Nov '12

27 Nov '12

Full_Name: Hallvard B Furuseth Version: 2.4.33 OS: URL: Submission from: (NULL) (193.69.163.163) Submitted by: hallvard mdb_env_open() with MDB_NOSYNC or MDB_NOMETASYNC does not open a sync descriptor, so resetting these flags does not work. Fixing.

1 0

Re: (ITS#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by hyc＠symas.com 27 Nov '12

27 Nov '12

hyc(a)symas.com wrote: > jvcelak(a)redhat.com wrote: >> Full_Name: Jan Vcelak >> Version: git master >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/jvcelak-121126-slapcat-fix-segfault-unable-… >> Submission from: (NULL) (209.132.186.34) >> >> >> Tool slapcat segfaults when there is an empty slapd.d config directory and >> 'slapcat -c -H ldap:///cn=config' is invoked. > > Not happening here: Your patch is invalid, but it appears there was a bug in the underlying back-ldif code. Still, it did not result in a SEGV. back-ldif is now fixed in master. > violino:~/OD/hobj/tests> ../servers/slapd/slapd -Tc -H ldap:///cn=config -d -1 > 50b538d7 slapcat init: initiated tool. > 50b538d7 slap_sasl_init: initialized! > 50b538d7 hdb_back_initialize: initialize HDB backend > 50b538d7 hdb_back_initialize: Berkeley DB 5.3.21: (May 11, 2012) > 50b538d7 mdb_back_initialize: initialize MDB backend > 50b538d7 mdb_back_initialize: MDB 0.9.4: (September 14, 2012) > 50b538d7 backend_startup_one: starting "cn=config" > 50b538d7 ldif_read_file: no entry file > "/usr/local/etc/openldap/slapd.d/cn=config.ldif" > 50b538d7 send_ldap_result: conn=-1 op=0 p=0 > 50b538d7 send_ldap_result: err=32 matched="" text="" > 50b538d7 could not stat config file "/usr/local/etc/openldap/slapd.conf": No > such file or directory (2) > slapcat: bad configuration file! > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by hyc＠symas.com 27 Nov '12

27 Nov '12

jvcelak(a)redhat.com wrote: > Full_Name: Jan Vcelak > Version: git master > OS: Linux > URL: ftp://ftp.openldap.org/incoming/jvcelak-121126-slapcat-fix-segfault-unable-… > Submission from: (NULL) (209.132.186.34) > > > Tool slapcat segfaults when there is an empty slapd.d config directory and > 'slapcat -c -H ldap:///cn=config' is invoked. Not happening here: violino:~/OD/hobj/tests> ../servers/slapd/slapd -Tc -H ldap:///cn=config -d -1 50b538d7 slapcat init: initiated tool. 50b538d7 slap_sasl_init: initialized! 50b538d7 hdb_back_initialize: initialize HDB backend 50b538d7 hdb_back_initialize: Berkeley DB 5.3.21: (May 11, 2012) 50b538d7 mdb_back_initialize: initialize MDB backend 50b538d7 mdb_back_initialize: MDB 0.9.4: (September 14, 2012) 50b538d7 backend_startup_one: starting "cn=config" 50b538d7 ldif_read_file: no entry file "/usr/local/etc/openldap/slapd.d/cn=config.ldif" 50b538d7 send_ldap_result: conn=-1 op=0 p=0 50b538d7 send_ldap_result: err=32 matched="" text="" 50b538d7 could not stat config file "/usr/local/etc/openldap/slapd.conf": No such file or directory (2) slapcat: bad configuration file! -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 27 Nov '12

27 Nov '12

--f46d042f95be98959504cf7fc847 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 28, 2012 at 12:06 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Tuesday, November 27, 2012 9:09 AM +0000 artemciy(a)gmail.com wrote: > > http://www.chiark.greenend.**org.uk/~sgtatham/bugs.html<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html> >> > > I would suggest you actually take the time to read what you link to. > Clearly, in this case, you have failed to do that. Yeah, too many letters. --f46d042f95be98959504cf7fc847 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Nov 28, 2012 at 12:06 AM, Quanah Gibson-Mount <span dir=3D"ltr">&lt= ;<a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</= a>></span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gma= il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= t:1ex"> --On Tuesday, November 27, 2012 9:09 AM +0000 <a href=3D"mailto:artemciy@gm= ail.com" target=3D"_blank">artemciy(a)gmail.com</a> wrote:<br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> <a href=3D"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" target=3D= "_blank">http://www.chiark.greenend.<u></u>org.uk/~sgtatham/bugs.html</a><b= r> </blockquote> <br> I would suggest you actually take the time to read what you link to. Clearl= y, in this case, you have failed to do that.</blockquote><div><br></div><di= v>Yeah, too many letters.</div></div> --f46d042f95be98959504cf7fc847--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by quanah＠zimbra.com 27 Nov '12

27 Nov '12

--On Tuesday, November 27, 2012 9:09 AM +0000 artemciy(a)gmail.com wrote: > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html I would suggest you actually take the time to read what you link to. Clearly, in this case, you have failed to do that. For example, under the section: "Show me how to show myself." This is the era of the Internet. This is the era of worldwide communication. This is the era in which I can send my software to somebody in Russia at the touch of a button, and he can send me comments about it just as easily. But if he has a problem with my program, he can't have me standing in front of it while it fails. "Show me" is good when you can, but often you can't. If you have to report a bug to a programmer who can't be present in person, the aim of the exercise is to enable them to reproduce the problem. You want the programmer to run their own copy of the program, do the same things to it, and make it fail in the same way. When they can see the problem happening in front of their eyes, then they can deal with it. So tell them exactly what you did. If it's a graphical program, tell them which buttons you pressed and what order you pressed them in. If it's a program you run by typing a command, show them precisely what command you typed. Wherever possible, you should provide a verbatim transcript of the session, showing what commands you typed and what the computer output in response. Give the programmer all the input you can think of. If the program reads from a file, you will probably need to send a copy of the file. If the program talks to another computer over a network, you probably can't send a copy of that computer, but you can at least say what kind of computer it is, and (if you can) what software is running on it. We're asking you to "Show us" what you did. Provide your code that caused an issue, since mdb is working fine with numerous projects. You are refusing to do provide code that shows what the issue is, and then expecting the developers to magically fix things with no relevant code path to examine. I don't understand your attitude in this at all. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7448) "assertion failed" in MDB
by hyc＠symas.com 27 Nov '12

27 Nov '12

Artem Grinblat wrote: > On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <hyc(a)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. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 27 Nov '12

27 Nov '12

--047d7b2e40c6a4d17e04cf7665de Content-Type: text/plain; charset=ISO-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=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(a)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--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by hyc＠symas.com 27 Nov '12

27 Nov '12

artemciy(a)gmail.com wrote: > --f46d042fddcee1dc8704cf74ca2b > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > >> 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. > > > Indeed, you might stress on 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 -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 26 Nov '12

26 Nov '12

--f46d042fddcee1dc8704cf74ca2b Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > 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. Indeed, you might stress on 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. That is not particularly helpful. :/ > > --Quanah > --f46d042fddcee1dc8704cf74ca2b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <span dir=3D"ltr"><= <a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a= >></span> wrote:=A0<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"> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"im">You can close the issue th= en, because I won't be producing one.<br> </div></blockquote> <br> I don't understand why you would take the time to report a bug, but the= n refuse to provide the information necessary to fix it.</blockquote><div><= br></div><div>Indeed, you might stress on=A0<a href=3D"http://www.openldap.= org/its/index.cgi">http://www.openldap.org/its/index.cgi</a> that bugs with= out a test case wouldn't be investigated so that people won't waste= their time.</div> <div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex= ;border-left:1px #ccc solid;padding-left:1ex"> =A0That is not particularly = helpful. :/<br> <br> --Quanah<br></blockquote><div><br></div></div> --f46d042fddcee1dc8704cf74ca2b--

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs