Re: Big Zenmap news

[jah <jah () zadkiel plus com>]

Attached is a patch for zenmap/setup.py which fixes a small typo which
causes the following when selecting the Topology tab after performing a
scan with --traceroute:

CRASH REPORTED:
SYS.PLATFORM: win32
OS.NAME: nt
Zenmap Version: 4.68
TRACEBACK:
Traceback (most recent call last):
  File "radialnet\gui\RadialNet.pyo", line 769, in expose
  File "radialnet\gui\RadialNet.pyo", line 157, in check_graph_status
  File "radialnet\gui\RadialNet.pyo", line 910, in __draw
  File "radialnet\gui\RadialNet.pyo", line 1056, in __draw_node
  File "radialnet\gui\Image.pyo", line 53, in get_pixbuf
GError: Failed to open file 'C:\Program
Files\Nmap\zenmap\share\zenmap\pixmaps\radialnet\padlock.png': No such
file or directory

Now, however, I've run into the following when selecting the topology tab:

CRASH REPORTED:
SYS.PLATFORM: win32
OS.NAME: nt
Zenmap Version: 4.68
TRACEBACK:
Traceback (most recent call last):
  File "radialnet\gui\RadialNet.pyo", line 769, in expose
  File "radialnet\gui\RadialNet.pyo", line 157, in check_graph_status
  File "radialnet\gui\RadialNet.pyo", line 910, in __draw
  File "radialnet\gui\RadialNet.pyo", line 1092, in __draw_node
MemoryError

The scan command was the "Regular Scan" profile to which I added an IP
address with prefix length and --traceroute.  This error (like the last)
resulted in several Crash reporting windows.

jah



--- setup.py.orig       2008-08-26 14:41:07.522384300 +0100
+++ setup.py    2008-08-26 14:44:09.303634300 +0100
@@ -70,7 +70,7 @@
                              glob(os.path.join(pixmaps_dir, '*.png'))),
 
                (os.path.join(pixmaps_dir, "radialnet"),
-                             glob(os.path.join(pixmaps_dir, "radialnet", '*.svg')),
+                             glob(os.path.join(pixmaps_dir, "radialnet", '*.svg')) +
                              glob(os.path.join(pixmaps_dir, "radialnet", '*.png'))),
 
                (config_dir, [os.path.join(config_dir, APP_NAME + '.conf')] +


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