https://bugzilla.novell.com/show_bug.cgi?id=387202 User hpj@urpla.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c101 --- Comment #101 from Hans-Peter Jansen <hpj@urpla.net> 2009-02-05 12:06:38 MST ---
The debuginfo packages are right there where Petr said in comment #77. Maybe you are confused that there's no nscd-debug{info,source}?
Yes.
That's because debug packages don't exist for subpacks (and nscd is one of glibc), you need to install glibc-debuginfo (-debugsource).
Done that already. As noted before, it would be MUCH easier for every tester, if Petr would provide a zypp compatible repo structure over there: Then people could add the repo target, update and install additional packages.
But indeed, more logs are not necessary I think, we see the assertions that cause nscd to exit. core file would be a bit more usefull. They aren't placed into the current pwd, but into the working dir of nscd, which usually is '/' (nscd chdir's into that one as daemon). You probably have some lying around there.
I got a nscd segfault (a few days ago) too, assertions also, but no core:
for f in $(locate core | egrep '\<core$'); do [ -f $f ] && l $f; done lrwxrwxrwx 1 root root 11 7. Jan 22:20 /dev/core -> /proc/kcore lrwxrwxrwx 1 root root 11 25. Dez 14:30 /lib/udev/devices/core -> /proc/kcore -rw-r--r-- 1 root root 213 3. Dez 08:26 /var/adm/perl-modules/yast2-core
For whatever reason, something prevents the kernel from creating a nscd core file. Since two people see this behavior, I bet you won't see ANY cores from somebody as long as you cannot tell us how! Read: try to simulate an assertion or segfault with nscd, and get it to produce one. I bet again, that this fails also. Now find the reason, tell us, and we're back into the game. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.