Re: [nmap-svn] r34034 - nmap

[jah <jah () zadkiel plus com>]

On 20/02/2015 03:48, Daniel Miller wrote:
> jah,
>
> This may be the case for Lua 5.3, but we are still using Lua 5.2 in the trunk. Please revert this, since it doesn't 
> work (all thread IDs are 0 from matching "0" in "0xABCD1234"
>
> Dan
>
> On Thu, Feb 19, 2015 at 9:07 PM, <commit-mailer () nmap org <mailto:commit-mailer () nmap org>> wrote:
>
>
>     this was before:-
>
>     NSE: Starting http-feed M:nil against ...
>     NSE: http-feed M:nil spawning new thread (thread: 02C63A78).
>     NSE: Finished http-feed W:nil against ...
>
>     this is now:-
>
>     NSE: Starting http-feed M:02D6EAF0 against ...
>     NSE: http-feed M:02D6EAF0 spawning new thread (thread: 02D6E640).
>     NSE: Finished http-feed W:02D6E640 against ...

Dan,

Sorry for committing that. I was mistaken to ascribe what I saw to a change in Lua 5.3 - I was actually using 5.2 (and 
trunk).

I'm seeing strange differences between the string representation of a coroutine on windows and linux, e.g.:-

win: "thread: 02D6E640"
lin "thread: 0x1e7c050"

Linux prefixes the ID with "0x" and the unprefixed ID is usually 7 (but sometimes 6) lower case hex chars. The last 
char is invariably "0".
Windows doesn't prefix the ID, it's invariably 8 upper case hex chars and the last char is either "0" or "8".

Leaving aside the length and low byte weirdness, the attached patch will deal with the prefix and case differences.

jah

Attachment: coroutine_string.patch
Description:

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