[Memory] Guid in-memory representation

[OMLinux]

Hi folks!

There's quite simple question for local gurus, but It's quite complicated to understand for me.
What is WoW object GUID in-memory representation?

As someone said here GUID is int64 (signed), but how I can convert HEX representation of GUID (something like 0x07000000065FF0F0). Is it in-memory representation of guid or (as I expect) number representation?

I converted this HEX to DEC with echo (cmd: echo "ibase=16; 7000000065FF0F0") but looks like it converts unsigned data. So should I consider MSB (as in-mem representation) or not? MSB - most significnt bit. For example (-7 = 1001 = -8 + 0 + 0 + 1). If yes. Is "0x07" MSB there or not?

Thanks in advance

[573737534947]

It is really only a plain int64. Integer are stored in little endian on x86, I don't really get what you are calculating there, but your guid "0x07000000065FF0F0" simply becomes F0 F0 5F 06 00 00 00 07 as byte sequence in memory going from left to right, from smaller address to bigger address and from lsb to msb. You can use a function like strtoull to convert it or write your own.

[OMLinux]

It is really only a plain int64. Integer are stored in little endian on x86, I don't really get what you are calculating there, but your guid "0x07000000065FF0F0" simply becomes F0 F0 5F 06 00 00 00 07 as byte sequence in memory going from left to right, from smaller address to bigger address and from lsb to msb. You can use a function like strtoull to convert it or write your own.

Thanx a lot

[daCoder]

0x07000000065FF0F0 = 504403158372446448
because it starts with a zero 07 = 00000111, you can't ignore the leading zeros.