> Has anyone came across strange clamd behaviour, when cli_calloc() > called from cli_scandesc() does NOT return? (yes, i know that cli_* come > from libclamav). It happens to me when I use process-based clamd. > Further investigation shows that the child process receives SIGSEGV on > calloc(). This is _not_ happening when using threading model. > Furthermore, it doesn't happen if MALLOC_CHECK_ enviroment variable is > exported, either set to 0, 1 or 2. My operating system is Linux/2.4.23 > [with Openwall patch applied].
Try changing the cli_calloc() code from y=calloc(x) to y=malloc(x) + memset(y, 0, x) On some implementations calloc() tries to return a different memory segment, that malloc() -- mainly windows, but who knows... MAYBE this could help... Besides, try using grsecurity instead of openwall. ---------- Tomasz Klim, [EMAIL PROTECTED] http://www.euroneto.pl Phone: +48 61 8433535 Fax: +48 61 8434455 Euronet Sp. z o.o., Dabrowskiego 81/85, 60-529 Poznan, Poland ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Clamav-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-devel
