How to deal when a memory address is used for different types

[hukasu]

The DLL that i am analyzing have some functions where a param is used initially with the value passed to it, but later in the function it is replaced by some other value with different type and semantic, if it were a local variable i would be able to Split Out as New Variable, but since it is a function param that option does not show, is there a way to inform that the stack location has a different type from its initial one from a instruction onwards?

[Wall-AF]

Not a great solution, but try creating a union of the 2 (or more) types.

[hukasu]

it worked better than the default behavior but there were other issues

i have to stop expecting a perfect output from the decompiler but i also wish to be able to reason about the output without having to remember all the failures in the decompilation

[Wall-AF]

You ought to try dealing with 16-bit Windows apps and segmentation!!!

[hukasu]

Found an open issue on this #975