Let's look at this very simple example: we have an AX (16-bit) register, which splits into two 8-bit registers: AH and AL (imagine x86). Then, imagine that these registers are memory mapped starting from RAM:0000 till RAM:0001 just like that:
AX - RAM:0x0000-0x0001 AH - RAM:0x0000 AL - RAM:0x0001
Is it possible to create a REG_DEFS for IDA Processor Module and then map it to the RAM segment in a way, that would allow tracking the registers in the correct order throughout the disassembly? The problem is, that commands such as
mov could operate on both "a complete" register (AX) as well as its parts (AH and AL) and while creating a RAM mapping, it doesn't allow me to name the same area of RAM twice using this code:
# Creating AX ida_bytes.create_data(0x0000, FF_WORD, 2, ida_idaapi.BADADDR) idc.set_name(0x0000, "AX", SN_CHECK) # This approach would fail, as it would intersect with AX and redefine it ida_bytes.create_data(0x0000, FF_BYTE, 1, ida_idaapi.BADADDR) idc.set_name(0x0000, "AH", SN_CHECK) ida_bytes.create_data(0x0001, FF_BYTE, 1, ida_idaapi.BADADDR) idc.set_name(0x0001, "AL", SN_CHECK)
So, I would either get AX in the disassembly listing or AH and AL, but not both. More than that:
- I need to be able to access individual bits within the AH and AL registers, therefore a simple UNION would not work I guess.
- IDA needs a way to understand that AH and AL are a part of the AX register and track not only their own values but a value as a part of AX as well. Example:
mov ax, 100h # AH should be 1h and AL should be 0
Is there a way to overcome it with the memory-mapped registers?