cpu_microcode_version changed type
willkg opened this issue · comments
I'm testing out 0.16.0 of the stackwalker and one thing i noticed is that the cpu_microcode_version changed from a u32 to a hexstring.
With v0.15.0, 6019f691-1acb-4357-a23f-b9d0f0230503 has a cpu_microcode_version of 244 and with v0.16.0, it has "0xf4".
The json_schema.md file says this value is a u32.
The v0.16.0 release notes have this line:
The stack walker will now fetch the CPU microcode value from the evil JSON payload
when it's not present in the minidump
Is it intentional that it's now a hexstring? If so, will the value always be a hexstring or is it possible that it will waffle between types depending on the value source?