I have tried to reproduce the bug, but I wasn't able to get the exact bug. I have successfully crashed Zenmap with no command option given in the zenmap profile configuration, but I cannot reproduce the missing heading error. Is is possible to give more information on the procedure to reproduce the missing heading error? Clearly, Zenmap should not crash as Daniel said, so this is what I should look for sure. Stop me if I am wrong please. Thanks.

No need to give any further details about missing heading error, because I read in the ConfigParser.py file that is "raised when a key-value pair is found before any section header".

I wonder if you know where is the source code (I mean the file) that show the bug dialog with OK button, and when you click on it, Zenmap crash.

Of course, we can modify ConfigParser.py, but I pretty sure no graphical code should be there, because this file is used to track down the errors.

A better solution is clearly to catch the error after pressing on OK button.

Related crash reports:

• http://seclists.org/nmap-dev/2013/q1/176
• http://seclists.org/nmap-dev/2013/q2/423
• http://seclists.org/nmap-dev/2013/q3/390 (file does not exist)
• http://seclists.org/nmap-dev/2013/q4/24 (Permission denied)
• http://seclists.org/nmap-dev/2013/q4/123 (Permission denied)
• http://seclists.org/nmap-dev/2014/q3/407 (Parsing errors)

Another crash report (non-color entered for a highlight color): http://seclists.org/nmap-dev/2016/q1/337