http://bugs.winehq.org/show_bug.cgi?id=24357
--- Comment #6 from Juan Lang juan_lang@yahoo.com 2010-09-13 22:21:22 CDT --- (In reply to comment #4)
One other thing I thought was weird was the address: fdfe4150. This comes from an earlier call to:
0009:Call ws2_32.inet_addr(004367b0 "80.65.254.253") ret=00403b0b 0009:Ret ws2_32.inet_addr() retval=fdfe4150 ret=00403b0b
So it converted the string "80.65.254.253" to the hex value 0xfdfe4150. I would think that the hex value should be 0x5041fefd since 0x50 = 80 0x41 = 65 0xfe = 254 0xfd = 253 But maybe this is just my lack of understanding of windows.
IP addresses are transmitted in "network order", which is big-endian. Intel CPUs are little-endian. Thus, the representation looks "backwards" on an Intel CPU. The address is correct as it is.