Re: Running xinetd 2.3.12

>Unfortunately I don't think a backtrace like this can 
>give you much info about what's going on. :-(

I tried setting up the same config and I'm still not
getting the problem. Based on the backtrace, malloc itself
died. This might be indicative of a stray pointer or
something that corrupted the heap.

My advice is to put valgrind on it. From the xinetd-2.3.12
directory run this:

valgrind --leak-check=yes --leak-resolution=med \
--num-callers=8 --logfile-fd=29 \
 ./xinetd/xinetd -d  29> log.txt

Then from another console do what you nornally do to
trigger a core dump. If it doesn't core, the issue a kill
-TERM to xinetd so that valgrind checks everything on exit.

Send the valgrind report. I think it will help nail this
down real quick.

-Steve Grubb


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com