Yeah I'm very familiar with 'file', I just wondered in what context one needs the ability to identify 38 machine languages, i.e. why does an organization deal with files containing unknown machine code, and have the need to identify them?
Sounds like maybe reverse engineering/security "research"-oriented work, perhaps.
I was basically leveraging my eidetic memory of opcodes and operands and its bitfields.
It all got started with writing pure assembly for Motorola 6502 (for arcades) and PDP-11 then eventually ended with ARM/RISC/MIPS. Most esoteric one is the Transmeta VLIW (TMS3200-02).
Comments
In what context was that used, if you can elaborate?
Like the UNIX file command, it lists out what the file content probably is/are.
It can also breakdown the file in question by regions and group such data content into most probable types … for each region.
As to its final application, that is not in my contract/task description.
Okay, thanks.
Yeah I'm very familiar with 'file', I just wondered in what context one needs the ability to identify 38 machine languages, i.e. why does an organization deal with files containing unknown machine code, and have the need to identify them?
Sounds like maybe reverse engineering/security "research"-oriented work, perhaps.
I was basically leveraging my eidetic memory of opcodes and operands and its bitfields.
It all got started with writing pure assembly for Motorola 6502 (for arcades) and PDP-11 then eventually ended with ARM/RISC/MIPS. Most esoteric one is the Transmeta VLIW (TMS3200-02).
and someone asked for one (internally).