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
Describe the bug
It's possible to rename 2 or more functions, all having the same name. This can cause confusion if it was not desired / an accident.
To Reproduce
Steps to reproduce the behavior:
Rename a function, for example to "function1".
Rename another function within the same scope to the same name "function1".
This works: The user now has 2 different functions with the same name.
This is highly confusing.
It's like having 2 children and giving them both the same name.
It's not forbidden, but makes everything extremely complicated.
Expected behavior
There should at least be a warning to the user that the same name is already in use.
Screenshots
Environment (please complete the following information):
Ghidra Version: 10.0.2
Ghidra Origin: official ghidra-sre.org distro
The text was updated successfully, but these errors were encountered:
This is expected behavior, manage your naming better if it's confusing, or use namespaces. I have 3 implementations of memcpy in my binary, I should name them differently than what they are because how they were linked in? No
Describe the bug
It's possible to rename 2 or more functions, all having the same name. This can cause confusion if it was not desired / an accident.
To Reproduce
Steps to reproduce the behavior:
Rename a function, for example to "function1".
Rename another function within the same scope to the same name "function1".
This works: The user now has 2 different functions with the same name.
This is highly confusing.
It's like having 2 children and giving them both the same name.
It's not forbidden, but makes everything extremely complicated.
Expected behavior
There should at least be a warning to the user that the same name is already in use.
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: