3 ms·

0xBuLL of 0xa bytes, dev's feelings come through loud and clear here.

• JoachimSchipper 10y ago
  You're looking at the output of a disassembler, not at the original source code. It probably reads something boring like sizeof(Identifier) in the original.
  • LeifCarrotson 10y ago
    That's exactly what it is. The third parameter to memcmp is the length of the buffers to be compared - "G847MC6JZ5", the string being compared, has a length of 11 characters (including the null terminator, which is a little odd). 11 is B in hex, and is stored as an unsigned Long Long, so the representation in the disassembler is 0xBuLL. And that string is the Blizzard identifier: https://www.virustotal.com/en/file/bdfd2017fb776b52a4604928e74bca9ca0d5bbe7b9d93782f94b0348e9f430bd/analysis/ https://www.virustotal.com/en/file/bdfd2017fb776b52a4604928e...
    • tomlogic 10y ago
      Not odd to include the null terminator if you want to ensure another string is "equal to", not just "starts with" the string you're comparing it to.
      • mzs 10y ago
        Dang it, I counted the \0 but miscounted the characters in the string.