Hi, I started nessusd with valgrind and obtained two memory management problems:
# valgrind --trace-children=yes nessusd ==5279== valgrind-1.0.0, a memory error detector for x86 GNU/Linux. ==5279== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward. ==5279== Estimated CPU clock rate is 870 MHz ==5279== For more details, rerun with: -v ==5279== ==5279== Conditional jump or move depends on uninitialised value(s) ==5279== at 0x4025775A: nasl_strdup (nasl_memory.c:95) ==5279== by 0x4025187D: execute_script (execute.c:106) ==5279== by 0x8056A55: nasl_plugin_add (nasl_plugins.c:80) ==5279== by 0x8055FF0: plugins_reload_from_dir (pluginload.c:136) ==5279== ==5279== Invalid read of size 4 ==5279== at 0x4025774B: nasl_strdup (nasl_memory.c:95) ==5279== by 0x4025187D: execute_script (execute.c:106) ==5279== by 0x8056A55: nasl_plugin_add (nasl_plugins.c:80) ==5279== by 0x8055FF0: plugins_reload_from_dir (pluginload.c:136) ==5279== Address 0x4025ED54 is not stack'd, malloc'd or free'd I am not sure whether valgrind has had any impact on the behaviour of nessusd because the nessusd is slowed down by a factor of, say, 30-50. Anyway, I think you should run valgrind occasionally. It is an invaluable tool for detecting tricky problems. FYI: You can find the tool here: http://developer.kde.org/~sewardj Michael -- ======================================================================= Michael Schmitt Telefon: +49 651 97551-40 Institut f�r Telematik Telefax: +49 651 97551-12 Bahnhofstrasse 30-32 WWW: http://www.ti.fhg.de D-54292 Trier E-Mail: mailto:[EMAIL PROTECTED] ======================================================================= - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
