Re: Segfault in LDAPerror() when errnum is out of bounds

Sean Burford wrote: > > 2009/3/20 Michael Ströder > > > many thanks for digging through this. Does that mean your issues with > syncrepl controls and l_ldap_result3() are fixed? > > Yeah. There are still mysteries, but RefreshOnly works well enough for now.

Re: Segfault in LDAPerror() when errnum is out of bounds

Hi, 2009/3/20 Michael Ströder > many thanks for digging through this. Does that mean your issues with > syncrepl controls and l_ldap_result3() are fixed? Yeah. There are still mysteries, but RefreshOnly works well enough for now. I'm wondering why controls are stripped from search results (i

Re: Segfault in LDAPerror() when errnum is out of bounds

Sean, many thanks for digging through this. Does that mean your issues with syncrepl controls and l_ldap_result3() are fixed? Any particular reason why you're using python-ldap 2.3.1 which is almost two years old? Sean Burford wrote: > When LDAPError receives an errnum from ldap_get_option(l, >

Segfault in LDAPerror() when errnum is out of bounds

Hi, When LDAPError receives an errnum from ldap_get_option(l, LDAP_OPT_ERROR_NUMBER, &errnum) that is out of bounds it causes a segfault. I have attached a script that triggers it and patch that fixes it. The test script requires an ldap URI and a BaseDN on the command line. The ldap server can