Ghidra: Use different names for a variable

[jrmuizel]

Is there some way to separate out uses of a variable and give them separate names.

i.e. sometimes a particular stack location or register is reused for a different purpose. It would be valuable to give this information to the decompiler so that it can treat it as a separate variable.

[kazblox]

It is surely something to be wanted.

[jrmuizel]

@emteere is there a recommended workflow to deal with this problem?

[Jaguar83]

I believe this should be labelled as a feature request.

[saruman9]

For registers you can do it:

1. Right click in the Decompiler → _Commit Locals_.
2. Right click on the variable → _Split out as New Variable_.

[Jaguar83]

4,883.64

For registers you can do it:

1. Right click in the Decompiler → _Commit Locals_.

2. Right click on the variable → _Split out as New Variable_.

I don't see this option in either the decompiler or the listing.

• OS: Windows 10
• Java Version: 11.0.6
• Ghidra Version: 9.1.2

[hostar]

The code is here, but I also have not been able to find this item in the right-click menu.

[Jaguar83]

Looking over the code, it seems that this only applies to locals that are declared within the function in the assembly listing. Even then, the varnode associated with the variable must have a "HighVariable" whatever that is.
There is no support for reusing parameters, renamed registers or other parameters that don't have whatever "HighVariable" is.