Re: Zenmap error: Char offset 64 is off the end of the line

[David Fifield <david () bamsoftware com>]

On Sat, Sep 06, 2008 at 01:30:19PM -0700, Fyodor wrote:
> I'm happy to report that David's setup.py fix allowed me to create a
> working Nmap Windows installer.  I tested Zenmap, and it worked
> against scanme.nmap.org.  But then I tried against a machine on my
> locan network and it crashed :(.  Here is the command:
>
> nmap -T Aggressive -A flog.yuma.net
>
> Zenmap reported:
>
> --
> "Gtk-ERROR **: Char offset 64 is off the end of the line
> aborting...
> [OK]
> --

We figured this bug out eventually. It had to do with Zenmap breaking
lines differently than PyGTK was in the syntax highlighting module.

The bug was uncovered because some script output has \r\r sequences in
it. (PyGTK was breaking lines between each \r, and Zenmap wasn't.) We
fixed the bug but the question arises: Where are the \r\r sequences
coming from?

It happens only on Windows. It may have to do with \r\n vs. \n line
endings. As far as I can tell it's only in script output. One case we
saw was using tab.lua for output.

David Fifield

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