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
Looking at PPCBE QNX binaries, will often see a function call that has a
complete and correct signature in the .plt section. Occasionally in the
binary, calls to this function will not have the correct number of arguments.
libsnmp.so.1 from exhibits this problem several times in the snmp_open
function.
I often use the "Override Call Type..." feature to force binaj to show the
call with the correct number of arguments.
Also, the "Override Call Type..." GUI default signature is very vanilla. It
is always:
void calltarget()
Would be more helpful to start with the current function signature (that the
user is tyring to change), or the function signature of the target function.
Steps To Reproduce:
Load PPCBE QNX binary.
Goto the .plt section, and look for pretty standard libc functions
Look at callrefs to function with known signatures and see that some have
decompilation with missing params
Expected Behavior:
Expected function signature shown for function in .plt section to be the same
as the decompiler shows for calls to the function
Screenshots/Video Recording:
Binary:
Sent binary via slack posting
Additional Information:
The text was updated successfully, but these errors were encountered:
Version and Platform (required):
Bug Description:
Looking at PPCBE QNX binaries, will often see a function call that has a
complete and correct signature in the .plt section. Occasionally in the
binary, calls to this function will not have the correct number of arguments.
libsnmp.so.1 from exhibits this problem several times in the snmp_open
function.
I often use the "Override Call Type..." feature to force binaj to show the
call with the correct number of arguments.
Also, the "Override Call Type..." GUI default signature is very vanilla. It
is always:
Would be more helpful to start with the current function signature (that the
user is tyring to change), or the function signature of the target function.
Steps To Reproduce:
decompilation with missing params
Expected Behavior:
Expected function signature shown for function in .plt section to be the same
as the decompiler shows for calls to the function
Screenshots/Video Recording:
Binary:
Sent binary via slack posting
Additional Information:
The text was updated successfully, but these errors were encountered: