Subject: Re: Performance of nmap. - msg#00082

Previous Message by Date: click to view message preview

Re: Performance of nmap.

On Fri, Jun 16, 2006 at 09:56:15PM +0200, majek04 wrote: > > I executed nmap with as many options as I could think of. > And I collected the results of gcov. > > My tests covered most of nmaps functions, but there are > about 50 left that I wasn't able to run by script. > The list is there: > http://ai.pjwstk.edu.pl/~majek/private/nmap/not-runned-functions.txt Cool. I went through the list and think they are all fine to stay except for "ServiceProbe::setName, which I have removed. I also removed most of the TCPIP_DEBUGGING stuff from tcpip.cc (except for a couple instances where I just want to keep them as they are in case I need to enable it in the future). I must admit to being a bit surprised that there wasn't more dead code :). We will make more when we port massping() to ultra_scan() and maybe trim down pos_scan to just handle rpc scan. > Maybe we can "#ifdef" these functions you suggested not to remove, > so that they won't be compiled for ordinary user? Well, there are only a few, and I think only one is of any significant length. And it would be more of a pain for me to compile them separately when I use them with the out-of-tree tools. So I'd probably rather just leave them alone for now. But if you find that any of them actually make a meaningful difference in executable size or runtime performance, let me know and we can find a solution. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev

Next Message by Date: click to view message preview

Umit 0.6.1-testing release announcement

Hi folks, Finally, a testing release from what I've been doing during this first month of Summer of Code. This release version is 0.6.1-testing, and is currently available for download at the source forge project page[1] in the following formats: * Source packages compressed in the formats: tar.gz, tar.bz2 and zip * Windows installer with Umit and Higwidgets only * Windows installer with Umit, Higwidgets and every related dependencies Windows users won't have any problem while installing Umit using the installers. Linux users should take a look at README file inside source packages for installation instructions. About this testing release: Umit has been running through great changes during this Summer of Code to turn into a more powerfull and stable tool for network administrators. But, as SoC students doesn't have much time for testing, and to much work to be done, I'll be releasing testing versions until the SoC deadline. These releases are intended to collect feedback from users and find some bugs, that are going to be fixed until the next stable release. If you did find any bug, please, register it at source forge project bug page[2], describing it as better as you can and if is that the case, try to send also the nmap command, output, and XML output that caused the problem. Try to be as clearer as possible, so I can fix it faster. ;-) What's new? * Colored Nmap output, with a preferences window that allow user to select wich colors he feels better with * New parser, about 6 times faster and able to manipulate nmap XML output files far greater than your computer memory can store * Fixed some save/load/close scan bugs. Now, Umit handles saving/loading better that before and closing a running scan leads to the process killing (currently only at Unix like OS). No ghost process anymore. * Now Umit doesn't show a terminal window while running a scan at windows. * Now you won't miss nmap errors (like non-root user errors). In the past, Umit wasn't behaving well with then, and was leading to a state that users were unable to understand what happened. * Fixed a bug at Compare Results window that was avoiding the save of diff files with arbitrary extension. Now you can save your diffs with an extension at the name. * Nmap colored output surprise for brazilian folks ;-) Links: [1] Umit project download page at source forge: https://sourceforge.net/project/showfiles.php?group_id=142490 [2] Umit project bug report page at source forge: https://sourceforge.net/tracker/?func=add&group_id=142490&atid=752647 [3] Umit repository (anonymous read access allowed): https://svn.sourceforge.net/svnroot/umit [4] Umit website: http://umit.sourceforge.net [5] Umit Blog: http://umitproject.blogspot.com PS: I forgot to change the version number at the About dialog, but don't worry: there will be more versions until the end of this Summer of Code, and I'll fix it until then. ;-) Cheeeeers! -- Adriano Monteiro Marques http://www.globalred.com.br http://umit.sourceforge.net py.adriano@xxxxxxxxx "Free software is a matter of liberty not price." (PYTHON powered) _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev

Previous Message by Thread: click to view message preview

Re: Performance of nmap.

On Fri, Jun 16, 2006 at 10:23:07PM +0200, majek04 wrote: > David Warde-Farley wrote: > > So, for memory leaks we have valgrind, electric fence, > google-perftools, dmalloc. It may be worth trying some of the commercial tools (if they offer a free trial) to see if they find anything useful. Like Rational Purify. Or Insure++. Or maybe there are better options. Here is a list which includes some such tools: http://www.cetus-links.org/oo_testing.html . > Maybe someone know tool similar to gcov/gprof? > (is there any replacement for windows?) I don't know if Visual Studio has any sort of profiler. If it does, it may not be in the free (Visual C++ Express) version I use. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev

Next Message by Thread: click to view message preview

Re: Performance of nmap.

Richard Moore wrote: > I'd check out callgrind (a valgrind skin, there's also a > nice from end for it > http://kcachegrind.sourceforge.net/cgi-bin/show.cgi > Great tool for me. Thanks. Marek Majkowski _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev