Re: Running xinetd 2.3.12

Thanks for the first patch Steve.
About the malloc() failure, I don't think I can install valgrind.
I've checked the sources, and apparently valgrind is not a single
executable I can move around. The "target" machine where all this
is happening is a system without a compiler, so in order to install
valgrind I would need to set up the sources in a separate build
environment. Not an option right now.
I don't have a "regular" linux server where I can try to reproduce
this "6-services-only" crash, so I guess I'll have to give up and
keep on using 2.3.3 :-(
Regards.
Marco

Steve G wrote:
> 
> >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
> _______________________________________________
> xinetd mailing list
> [email protected]
> http://www.xinetd.org/mailman/listinfo/xinetd