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
The code under this TODO currenty updates the parameter name and type if that parameter is being passed through a register. If you try to change the parameter for a stack var argument, like the second parameter of entry() in the fauxware test binary, the change will not go through. Below is some example libbs code that demonstrates the problem:
When running the above with the DecompilerInterface connected to Ghidra with the fauxware binary loaded, you should see that the first parameter, the one passed by register, updates fine but the second one, a stack var, remains unchanged.
The text was updated successfully, but these errors were encountered:
Flipout50
changed the title
Fix Ghidra Function Header Parameter Name and Typeing for Stack Variables
Fix Ghidra Function Header Parameter Name and Typing for Stack Variables
Apr 3, 2024
https://github.com/binsync/libbs/blob/7928b24511eb82dd52f06fb1f9fc52e98bc2735a/libbs/decompilers/ghidra/interface.py#L355C32-L355C40
The code under this TODO currenty updates the parameter name and type if that parameter is being passed through a register. If you try to change the parameter for a stack var argument, like the second parameter of entry() in the fauxware test binary, the change will not go through. Below is some example libbs code that demonstrates the problem:
When running the above with the DecompilerInterface connected to Ghidra with the fauxware binary loaded, you should see that the first parameter, the one passed by register, updates fine but the second one, a stack var, remains unchanged.
The text was updated successfully, but these errors were encountered: