Backtrace on failed OpenLDAP to Samba 4 AD LDIF Conversion.

Michael Wood esiotrot at gmail.com
Wed Jun 8 01:36:18 MDT 2011


On 8 June 2011 09:11, Zombie Ryushu <zombie_ryushu at yahoo.com> wrote:
> What I am doing is converting the stock OpenLDAP 2.4.25 Schema files on Mandriva 2010.2 from /usr/share/openldap/schema/* I generally copy them to my home directory and run oLschema2ldif4 -I core.schema -b DC=MDVGROUP -O core.ldif - Usually it results in a segfault for core.schema and cosine.schema. Other schemas create other problems. running it through gdb I can get:
>
> This.
>
> Starting program: /usr/bin/oLschema2ldif4 -I core.schema -b DC=MDVGROUP
>  -O core.ldif
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff6c25380 in strcasecmp () from /lib64/libc.so.6
> Missing debug package(s), you should install: cyrus-sasl-debug-2.1.23-8mdv2010.1.x86_64 e2fsprogs-debug-1.41.12-1mnb2.x86_64 glibc-debug-2.11.1-8.2mnb2.x86_64 gnutls-debug-2.8.6-1mdv2010.1.x86_64 libgcrypt-debug-1.4.5-1mdv2010.1.x86_64 libgpg-error-debug-1.7-2mdv2010.1.x86_64 libtasn1-debug-2.6-2mdv2010.1.x86_64 openldap-debug-2.4.22-2.2mdv2010.2.x86_64 openssl-debug-1.0.0a-1.7mdv2010.2.x86_64 popt-debug-1.15-9mdv2010.1.x86_64 zlib-debug-1.2.3-15mdv2010.1.x86_64
> (gdb) bt
> #0  0x00007ffff6c25380 in strcasecmp () from /lib64/libc.so.6
> #1  0x00007ffff75667cf in find_syntax_map_by_standard_oid () from /usr/lib64/samba4/libldbsamba.so
> #2  0x0000000000402b94 in process_entry ()
> #3  0x0000000000403726 in main ()
> (gdb) bt full
> #0  0x00007ffff6c25380 in strcasecmp () from /lib64/libc.so.6
> No symbol table info available.
> #1  0x00007ffff75667cf in find_syntax_map_by_standard_oid () from /usr/lib64/samba4/libldbsamba.so
> No symbol table info available.
> #2  0x0000000000402b94 in process_entry ()
> No symbol table info available.
> #3  0x0000000000403726 in main ()
> No symbol table info available.
> (gdb) q
> A debugging session is active.

Try compiling with debug symbols (e.g. ./configure.developer).  That
should give more information about what went wrong.

-- 
Michael Wood <esiotrot at gmail.com>


More information about the samba-technical mailing list