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
I'm working on a 16-bit MS-DOS executable. As you can see on this screenshot (from a previous bug report) the decompiler shows ram0x004502, which when double clicking seems to point to 0000:4502.
However, I've correctly assigned the DS register for this function (and it's obviously not 0x0000), but the decompiler seems to ignore it.
Am I doing something wrong, or does the decompiler not take into account the DS register when dereferencing memory? Can I fix/workaround this somehow?
This discussion was converted from issue #973 on March 21, 2023 14:46.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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
-
I'm working on a 16-bit MS-DOS executable. As you can see on this screenshot (from a previous bug report) the decompiler shows
ram0x004502, which when double clicking seems to point to0000:4502.However, I've correctly assigned the
DSregister for this function (and it's obviously not0x0000), but the decompiler seems to ignore it.Am I doing something wrong, or does the decompiler not take into account the
DSregister when dereferencing memory? Can I fix/workaround this somehow?Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions