You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the architecture is implemented with no support for temp registers. It appears that binja will automatically create some during it's analysis and it's not clear how we need to handle them for the lookups. This is specifically the case in the llil view when clicking on cond:<n> which are implemented as temporary registers. Doing so causes:
invalid register id 4294967295
invalid register id 4294967295
invalid register id 4294967295
to be spammed to the log. This corresponds to a register number of -1. The issues is definitely our handling of register but it's unclear what the correct way to handle this is because it's not clear how temporary registers are automatically created within binja. It only appears to happen in in llil. Unclear why the behavior doesn't happen in mllil or hlil.
The text was updated successfully, but these errors were encountered:
Currently the architecture is implemented with no support for temp registers. It appears that binja will automatically create some during it's analysis and it's not clear how we need to handle them for the lookups. This is specifically the case in the llil view when clicking on
cond:<n>
which are implemented as temporary registers. Doing so causes:to be spammed to the log. This corresponds to a register number of -1. The issues is definitely our handling of register but it's unclear what the correct way to handle this is because it's not clear how temporary registers are automatically created within binja. It only appears to happen in in llil. Unclear why the behavior doesn't happen in mllil or hlil.
The text was updated successfully, but these errors were encountered: