#122 slptool findsrvs gives segfault

[Anonymous]

When SA and DA configured in same network . SA enabled for ipV6 and ipV4 both , DA enabled for ipV4. In this environment if we run "slptool findsrvs service:wbem" then it gives segmentation fault immediately after SA registers to DA and it continues to behave so untill we stop DA and restart SA. This issue is seen when we run slptool from same system where SA is configured. Stack trace of core generated is as follows :

Loaded symbols for /opt/ibm/icc/lib/libslp.so.1
Reading symbols from /lib/libcrypto.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.6
Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Core was generated by `./slptool findsrvs service:wbem'.
Program terminated with signal 11, Segmentation fault.
#0 0xf7fe4aa5 in KnownDADiscoveryCallback () from /opt/ibm/icc/lib/libslp.so.1

[Steve McIntyre]

Hi,

Looking for any more information on this bug report; I'm investigating on behalf of Debian, and I'm struggling to even reproduce this problem as it stands...