https://bugzilla.novell.com/show_bug.cgi?id=387202 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=387202#c100 --- Comment #100 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-05 07:58:42 MST --- (In reply to comment #98)
The debuginfo packages are right there where Petr said in comment #77. Maybe you are confused that there's no nscd-debug{info,source}? That's because debug packages don't exist for subpacks (and nscd is one of glibc), you need to install glibc-debuginfo (-debugsource).
Well, if you want me to install something in order to produce the coredump, tell me what exactly do I install.
Also, Carlos: you didn't yet follow the guidelines of comment #66. You still use persistent databases. Yes, the comment talks about setting it to "0". Of course instead you should use "no" for all databases you have in nscd.conf. See nscd.conf(5).
No, I didn't, I said in #88 and #91 that I needed clarification. I still do. Do you mean I should use: persistent whatever no
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.
One of the crashes was not an assertion but a segfault. No, there is no core on /. I can run an "updatedb; locate corewhatever", but I need to know the exact name to search for, because it yields up of 5713 entries. Or alternatively, an exact "find" command to find it. As far as I can see, there is no core in: / /tmp /var/run/nscd /root/Bugzilla/Bug_387202 <-- pwd where I run "nscd -d" /root /home/cer Note: the "nscd -d" command runs on an xterm where I did "su -" to root, in order to keep an eye on it. The xterm is under gnome. I remember some mention years ago of X blocking coredumps. But somebody here said he managed to produce coredumps with a code dividing by zero, so it must be nscd which impedes them :-? Suggestion: search for all assertions in the code and replace/add logger calls. In my programming days, an assertion was the last resource to use, and never in production code. It was used instead of proper code to find an unexpected situation, never as error handling code. -- 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.