Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback

[steve@falchion.com]

On Tue, 2009-07-21 at 11:17 -0700, Howard Chu wrote:
> Steve Paras-Charlton wrote:
> > On Tue, 2009-07-21 at 10:32 -0700, Howard Chu wrote:
> >> steve@falchion.com wrote:
> >>> 2.4.17 fails in an identical manner.
> >>>
> >>> For those interested, 2.4.17 failed to compile because the installed
> >>> 2.4.16 libs were being picked up instead of the freshly compiled ones
> >>> during the link phase.
> >>
> >> Looks like a problem in your OpenSSL build, not in OpenLDAP.
> >
> > Any ideas what that problem might be  or what leads you to believe this?
> 
> The backtrace shows that these SSL functions are contained inside your 
> libldap_r shared library object file. Usually they should be present in 
> OpenSSL's own shared libraries. If OpenSSL was only provided as a static 
> library, it's not clear that their code will behave correctly when used inside 
> a shared library (i.e., PIC vs non-PIC dependencies).

Thanks for that info.  I apologize for my ignorance but I got out of
code development 15-20 years ago.  Would it help if I compiled slapd
statically?  Is there an option for that in configure?

> 
> > Unfortunately this OpenSSL is the one distributed by IBM as part of the
> > AIX operating system, so it's not really my build...  If I'm going to go
> > to them with this, I could use a little more ammo :)
> 
> It would also help if you compile without optimization, with debug symbols, 
> and run the non-stripped binaries. Your backtraces are lacking a lot of info 
> at the moment.

I re-configured with --enable-debug and re-compiled, then ran  slapd
from the servers/slapd directory and got the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1]
0xd2514a34 in SSL_CTX_set_info_callback ()

from /LDAP/build/openldap-2.4.17/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2)
(gdb) bt
#0  0xd2514a34 in SSL_CTX_set_info_callback ()

from /LDAP/build/openldap-2.4.17/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2)
#1  0xd2512118 in tlso_ctx_init ()
from /LDAP/build/openldap-2.4.17/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2)
#2  0xd250e70c in ldap_int_tls_init_ctx ()

from /LDAP/build/openldap-2.4.17/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2)
#3  0xd2510400 in ldap_pvt_tls_set_option ()

from /LDAP/build/openldap-2.4.17/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2)
#4  0x10001fb0 in main ()


To my relatively untrained eye this doesn't look much different from the
original.  Can you give me an example of how I could compile and run to
produce a better stack trace?  I couldn't find documentation of that
sort on the OpenLDAP web page...

Thanks again,
Steve

> 
> >
> > Steve
> >
> >>>
> >>> Steve
> >>>
> >>> On Mon, 2009-07-20 at 20:04 -0700, Steve Paras-Charlton wrote:
> >>>> Currently 2.4.17 fails to compile under AIX 5.3TL10, so I'll try to work
> >>>> on it, but in the meantime, any ideas why 2.4.16 is crashing thus?
> >>>>
> >>>> Steve
> >>>>
> >>>> On Mon, 2009-07-20 at 15:58 -0700, Quanah Gibson-Mount wrote:
> >>>>> --On Monday, July 20, 2009 3:52 PM -0700 Steve Paras-Charlton
> >>>>> <steve@falchion.com>   wrote:
> >>>>>
> >>>>>> Haven't tried it.  is it stable now (or soon to be?)
> >>>>>
> >>>>> I'd assume that depends on what bugs people report against it.  Knowing
> >>>>> whether or not this affects 2.4.17 would certainly be useful in that
> >>>>> determination. ;)
> >>>>>
> >>>>> --Quanah
> >>
> >
> >
> 
>