I have the same problem.
After starting unscd it segfaults after a short time.
If many requests occur virtually immediatly.
The attached output of valgrind supports this claim:
valgrind -v --leak-check=full --show-leak-kinds=all --trace-children=yes nscd -d 2>&1 | tee /tmp/valgrind.log
...
==2487== Process terminating with default action of signal 11 (SIGSEGV)
==2487== Access not within mapped region at address 0x0
==2487== at 0x403B71: free_refcounted_ureq (nscd.c:1220)
==2487== by 0x403C72: close_client (nscd.c:808)
==2487== by 0x402544: handle_client (nscd.c:1602)
==2487== by 0x402544: main_loop (nscd.c:2027)
==2487== by 0x402544: main (nscd.c:2654)
...
This points to line 1220 in nscd.c as the source of the problem.
Problem appears to be fixed in unscd_0.52-1 (there was a NULL check added at exactly this code position).
Also installing a manually build package of unscd_0.52-1 fixes the problem.
Obvious resolution would be to provide an official unscd_0.52-1 package for 14.04
I have the same problem.
After starting unscd it segfaults after a short time.
If many requests occur virtually immediatly.
The attached output of valgrind supports this claim: leak-kinds= all --trace- children= yes nscd -d 2>&1 | tee /tmp/valgrind.log
valgrind -v --leak-check=full --show-
... _ureq (nscd.c:1220)
==2487== Process terminating with default action of signal 11 (SIGSEGV)
==2487== Access not within mapped region at address 0x0
==2487== at 0x403B71: free_refcounted
==2487== by 0x403C72: close_client (nscd.c:808)
==2487== by 0x402544: handle_client (nscd.c:1602)
==2487== by 0x402544: main_loop (nscd.c:2027)
==2487== by 0x402544: main (nscd.c:2654)
...
This points to line 1220 in nscd.c as the source of the problem.
Problem appears to be fixed in unscd_0.52-1 (there was a NULL check added at exactly this code position).
Also installing a manually build package of unscd_0.52-1 fixes the problem.
Obvious resolution would be to provide an official unscd_0.52-1 package for 14.04