The trace doesn't help me much in tracking it down I'm afraid. I've checked all the uses of strcmp() in nslcd that could be reachable and have not found a likely candidate. You could try building a package on another machine that includes the debug symbols (see https://jameswestby.net/tips/tips/compiling-debian-package-for-debug.html) or try running nslcd under valgrind. Running under valgrind does have a performance impact though.
Is the crash always after such a search? Is there any pattern in the crashes?
The trace doesn't help me much in tracking it down I'm afraid. I've checked all the uses of strcmp() in nslcd that could be reachable and have not found a likely candidate. You could try building a package on another machine that includes the debug symbols (see https:/ /jameswestby. net/tips/ tips/compiling- debian- package- for-debug. html) or try running nslcd under valgrind. Running under valgrind does have a performance impact though.
Is the crash always after such a search? Is there any pattern in the crashes?