4
The issue here is not strings, it's the fact that Hex-Rays didn't guess the right calling convention for sub_4022E0. Notice that the disassembly listing moves values into both ecx and edx before the call, whereas the decompilation for that call shows only one argument? Hex-Rays thinks there's only one argument -- maybe even only one stack argument -- whereas ...
1
That's extremely common. Sometimes Hex-Rays recognizes these patterns, sometimes it doesn't. Get used to recognizing them visually, writing a comment if necessary, and moving on.
Only top voted, non community-wiki answers of a minimum length are eligible
Related Tags
hexrays × 106ida × 89
decompilation × 24
idapython × 12
c++ × 9
decompiler × 9
c × 7
disassembly × 6
ida-plugin × 6
assembly × 5
x86 × 4
arm × 4
idapro-sdk × 4
windows × 3
ghidra × 3
float × 3
msvc × 3
array × 3
debugging × 2
firmware × 2
mips × 2
decompile × 2
stack-variables × 2
virtual-functions × 2
local-variables × 2