Re: Bug Report - Zenmap v6

[David Fifield <david () bamsoftware com>]

On Wed, Jun 20, 2012 at 02:19:36AM +0000, Topaz Aral wrote:
> Hi David,
>
> Please see the results below: 
>
> running: nmap -T4 -A -v -F 172.16.3.0-62 
> result:
>       Problem signature:
>         Problem Event Name:   APPCRASH
>         Application Name:     zenmap.exe
>         Application Version:  6.0.0.0
>         Application Timestamp:        49180193
>         Fault Module Name:    libglib-2.0-0.dll
>         Fault Module Version: 2.28.8.0
>         Fault Module Timestamp:       4e253544
>         Exception Code:       40000015
>         Exception Offset:     0004c2d8
>         OS Version:   6.1.7601.2.1.0.272.7
>         Locale ID:    3081
>         Additional Information 1:     0e2a
>         Additional Information 2:     0e2a79fd2f6a14357ab547552aeb31b7
>         Additional Information 3:     42fe
>         Additional Information 4:     42fea5f3025b8aa4aa244a8c26dc1ed0
>
> running: nmap -T4 -A -v -F scanme.nmap.org
> result: worked fine
>
> running: nmap -T4 -A -v -p 1-65535 scanme.nmap.org
> result: worked fine
>
> VM Is reserved 4GB of memory.
> Task Manager resports <1GB being used and CPU usage hovering around 2-10
> percent

For what it's worth, I tried this exact command line on Windows 7, with
interface aliases populating the 172.16.3.0-62 range. I didn't get any
crash.

What's really strange is that this appears to be crashing in glib, which
may be some kind of bug in GTK+. Clearly, something that Nmap is trying
to display is causing this bug, but we don't know what it is.

It would help if you could narrow down the crashing command even more.
Try scanning 172.16.3.0-31, then 172.16.3.0-62. If one of those crashes
but the other doesn't, continue bisecting that IP range. See if you can
isolate it to a single IP address.

Please run the same command in the terminal, as follows:

nmap -T4 -A -v -F 172.16.3.0-62 -oA zenmap-crash

This will create files zenmap-crash.nmap and zenmap-crash.xml. Send
those files to me, and I will try opening them to see if they cause a
crash.

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