From: Steve G <lin...@ya...> - 2003-12-26 13:37:34
|
Hi, I stepped up to the latest 2.1.0 release and was happy to see new bugs being reported for the first time. I was testing against the cvs copy of xinetd and I see this: Warning: invalid file descriptor -1 in syscall close() OK, we set some descriptors to -1 when they have been previously closed and I'd like to find this bug...but there's no location information given in the output. No stack trace. Is there a way to enable this? I'm 100% sure this is an xinetd bug, I'd like to fix it. Another thing that xinetd does on startup is close all file descriptors between 2 & FD_SETSIZE or lim_max as returned by getrlimit() (or getdtablesize if RLIMIT_NOFILE is not available), whichever is lower. The curious things is that valgrind started reporting close syscall errors from 821-1023. Where is valgrind getting the 821 from? Xinetd does try to set the fd limit by using setrlimit. Valgrind should be able to track this value since it intercepts syscalls. The reason I'm curious is that it seems xinetd or valgrind is miscalculating the maximum fd number. Thanks, Steve Grubb __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ |