Re: Crash report

[Jacek Wielemborek <d33tah () gmail com>]

10/04/2014 06:47:49 Daniel Miller <bonsaiviking () gmail com>:
> On Wed, Apr 9, 2014 at 9:09 PM, jim.bishop () siriuscom com <
>
> jim.bishop () siriuscom com> wrote:
> > Doing the following scan:
> >
> > nmap -p 443 -O -d3 --open --version-light --script ssl-heartbleed TARGET
> > LIST
> >
> > Getting this error:
> >
> > Version: 6.40b
> >
> > Traceback (most recent call last):
> >   File "zenmapGUI\ScanNmapOutputPage.pyo", line 247, in _row_changed
> >   File "zenmapGUI\ScanNmapOutputPage.pyo", line 267, in _update
> >   File "zenmapGUI\NmapOutputViewer.pyo", line 291, in show_nmap_output
> >
> > MemoryError
>
> Jim,
>
> Thanks for the report. Unfortunately, this error simply means that your
> system does not have enough memory for the scan you requested. Luckily, the
> memory hog is not Nmap itself, but the Zenmap front-end. If you run the
> scan on the command line just as you specified it, it should not run into
> this same problem. Then you can import the results into Zenmap if you like
> for viewing.
>
> Dan
> _______________________________________________
> Sent through the dev mailing list
> http://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/

I'm getting the impression that Zenmap should catch that and let the user know 
in a more meaningful way.

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/