On 2024/01/30 9:24, nilayvaish(a)google.com wrote: thanks for the information. I can see that there is the orc_header symbol and data also in a vmcore, so maybe it can be read easily: crash> whatis orc_header const u8 orc_header[20]; crash> rd -8 orc_header 20 ffffffffb718ef94: fe 5d 32 bf 58 1b d6 3b 2c a9 a5 c6 5b a5 a6 25 ... ffffffffb718efa4: ea b3 fe 24 but it's a hash, not a version number, how are you going to use this? Does crash have to have all historical hash values? all of format changes do not affect crash's unwinder though. Thanks, Kazu > > I do not have familiarity with the code for the crash utility. Is it possible for someone to advise on whether the above sounds reasonable? If yes, then how to divide the functionality among the files? If no, then what would a reasonable to have this functionality? > > Thanks! > -- > Crash-utility mailing list -- devel(a)lists.crash-utility.osci.io > To unsubscribe send an email to devel-leave(a)lists.crash-utility.osci.io > https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/ > Contribution Guidelines: https://github.com/crash-utility/crash/wiki

On 2024/02/06 6:18, nilayvaish(a)google.com wrote: for example, you can get it like this in x86_64_ORC_init. unsigned char buf[20]; if (try_get_symbol_data("orc_header", sizeof(buf), buf)) { ... It's good to be able to notice the change of the ORC format easily, but not all of changes affect crash, so for unknown values I think it should be a warning at most. Thanks, Kazu