Browsing Persian translation

35.

How to Report a Bug

36.

<big><b>How to report a bug</b></big>

Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from <b>%(nmap_web)s</b>. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <b>&lt;dev@nmap.org&gt;</b>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to dev@nmap.org are far more likely to be answered than those sent to Fyodor directly.

Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at https://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.

37.

Crash Report

38.

An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the <a href="mailto:dev@nmap.org">dev@nmap.org</a> mailing list. (<a href="http://seclists.org/nmap-dev/">More about the list.</a>) The developers will see your report and try to fix the problem.

39.

<b>Copy and email to <a href="mailto:dev@nmap.org">dev@nmap.org</a>:</b>

40.

Scan Output

41.

Select Scan Result

42.

Error parsing file

43.

The file is not an Nmap XML output file. The parsing error that occurred was
%s

44.

Cannot open selected file