Hi,
When i am running a particular user space program ( compiled in
sles9.2) on a test box running RHEL6.1 it coredumps as below.
NOTE the core dump only happens when run as a ldap configured user
but works fine when run as non-ldap user.

Reading symbols from /usr/lib/libstdc++.so.5...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libstdc++.so.5
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Core was generated by `smcli lsbundle'.
Program terminated with signal 11, Segmentation fault.
#0 0x080494e0 in ?? ()
Missing separate debuginfos, use: debuginfo-install compat-libstdc++-33-3.2.3-69.el6.i686 glibc-2.12-1.25.el6.i686 libgcc-4.4.5-6.el6.i686
(gdb) where
#0 0x080494e0 in ?? ()
#1 0x0804b736 in ?? ()
#2 0x00126cc6 in __libc_start_main () from /lib/libc.so.6
#3 0x08049361 in ?? ()
(gdb)

NOTE that when the same user space program is run under rhel5.6
it also works fine

Is this something related to bad library or build issue or something
totally different ?

Some more data based on my debug.
It eventually points at something related to RHEL6.1 and user being a ldap user.
Are there any ldap related defaults that were changes between rhel5 and rhel 6 ? That might provide some clues....

On your SLES system you can make your executable "self-containing" using
Ermine (http://magicErmine.com) or statifier (http://statifier.sf.net)

If you are using Ermine, make sure you specify --with-nss=internal switch
If you are using statifier, make sure you preloaded all NSS libraries.