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
In the snippet regarding the extraction of arguments, if I'm understanding the code correctly, is iterating through all the instructions until it reaches a CALL and then check again that the address is the one we are interested in, but it's possible to ask for the opcode directly from an address passing it as an argument to getPcodeOps()
From the help:
>>> help(high_func.getPcodeOps)
Searching API for ghidra.program.model.pcode.HighFunction.getPcodeOps()...
Searching API for ghidra.program.model.pcode.PcodeSyntaxTree.getPcodeOps()...
-----------------------------------------------------
Iterator getPcodeOps()
return all PcodeOps (alive or dead) ordered by SequenceNumber
@return java.util.Iterator<ghidra.program.model.pcode.PcodeOpAST>: -- Iterator to PcodeOps
-----------------------------------------------------
-----------------------------------------------------
Iterator getPcodeOps(Address addr)
return all PcodeOps associated with a particular instruction Address
@param addr (ghidra.program.model.address.Address): -- Address of instruction generating PcodeOps
@return java.util.Iterator<ghidra.program.model.pcode.PcodeOpAST>: -- Iterator to PcodeOps
-----------------------------------------------------
In the snippet regarding the extraction of arguments, if I'm understanding the code correctly, is iterating through all the instructions until it reaches a
CALL
and then check again that the address is the one we are interested in, but it's possible to ask for the opcode directly from an address passing it as an argument togetPcodeOps()
From the help:
From a terminal session
In this way you can avoid a lot of overhead.
The text was updated successfully, but these errors were encountered: