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
Using x86-16.cspec for a Windows 3.1X application suit, Ghidra seems to be shrinking a 32-bit value (caused by the 0x66 operand size override prefix) into a 16-bit one with the effect of generating a temporary (non-stack) variable of 16-bits instead of the correctly sized stack variable. Can anyone shed light on why, and how to correct it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Using
x86-16.cspec
for a Windows 3.1X application suit, Ghidra seems to be shrinking a 32-bit value (caused by the0x66
operand size override prefix) into a 16-bit one with the effect of generating a temporary (non-stack) variable of 16-bits instead of the correctly sized stack variable. Can anyone shed light on why, and how to correct it?Below is the pcode for the
SHR
instructionthat results in
where
iVar3
is of typeint
instead of(u)long
!Trying to change the type causes

Beta Was this translation helpful? Give feedback.
All reactions