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
Just started playing with Ghidra. Have old x86 code with code segment and data segment. Ghidra automatically finds most of the DS strings and I understand why it misses some and how to patch. But no matter what I try, the code in disassembler and decompiler shows the 16b address in DS and not the string value in double quotes. I set the search default to Constant in the string search, which some searches suggested helps but no difference. I saw an issue about pointer sizes 16b (with implied DS) vs 32b, which seems related, but not sure it helps me. Is there any way to get around this? Please be explicit, newbie with the tool.
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
-
Just started playing with Ghidra. Have old x86 code with code segment and data segment. Ghidra automatically finds most of the DS strings and I understand why it misses some and how to patch. But no matter what I try, the code in disassembler and decompiler shows the 16b address in DS and not the string value in double quotes. I set the search default to Constant in the string search, which some searches suggested helps but no difference. I saw an issue about pointer sizes 16b (with implied DS) vs 32b, which seems related, but not sure it helps me. Is there any way to get around this? Please be explicit, newbie with the tool.
Beta Was this translation helpful? Give feedback.
All reactions