No method is perfect, the limitations below are:
- the .MAP file will include functions that the linker cannot resolve (for example, overriding methods in classes affected by your code).
- it will only give you method names, but if the methods are overloaded, you can use several versions of these methods
The big pro with .MAP files is that they are easier to scan than the blue dots in the code editor.
This way it answers your question to provide a list of functions. But in fact, this may not be the case (:
Method using the .MAP file:
- modify the project to include a detailed .MAP file
- rebuild your project
- the directory of your .EXE file will now contain the .MAP file
- scan .MAP file for function names included in .EXE
This .MAP file will exclude functions eliminated by the compiler and linker.
This is a good sign that you have a dead code.
Similarly, you can use JDBG information. This contains more context, but also requires that you record some instruments yourself.
source share