RE: Failed assertion

["Sina Bahram" <sbahram () nc rr com>]

Well, I'll simply compile as release and give it a wurl

Thanks for this

Should the asert be modified to acount for this possibility?

Take care,
Sina 

-----Original Message-----
From: Thomas Buchanan [mailto:TBuchanan () thecompassgrp net] 
Sent: Friday, May 18, 2007 5:38 PM
To: Sina Bahram
Cc: nmap-dev () insecure org
Subject: RE: Failed assertion


> -----Original Message-----
> From: nmap-dev-bounces () insecure org
> [mailto:nmap-dev-bounces () insecure org] On Behalf Of Sina Bahram
> Sent: Friday, May 18, 2007 4:16 PM
> To: nmap-dev () insecure org
> Subject: Failed assertion
<snip>
> ***
>
> Then I got the following in a windows dialog box with "retry" 
> and "ignore"
> and "abort", and then I got the "nmap has encountered a problem and 
> needs to close" dialog.
>
> ***
>
> File: isctype.c
>
> Line: 56
>
> Expression: (unsigned)(c + 1) <= 256
>
> ***
>
> Ideas?
>
> Take care,
> Sina

Sina,

I ran into this issue a little while ago on my development system (Windows
XP SP2 with MS Visual C++ 2005 Express Edition), and solved it by switching
the build profile from Debug to Release.  If I recall, I think I traced the
issue to (what I think is) a non-ASCII character in the following line of
the nmap-mac-prefixes file:

Line 7040:

001BA1 Åmic AB

BTW that line was introduced via SVN rev 4602, which was an update to the
latest IEEE data.

You might try removing that line from the file if you still want to run the
Debug builds.

Hope this helps,

Thomas


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