Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow ghidra decompiler to follow types of the caller. #30

Open
Escapingbug opened this issue Jul 3, 2021 · 0 comments
Open

Allow ghidra decompiler to follow types of the caller. #30

Escapingbug opened this issue Jul 3, 2021 · 0 comments
Assignees
@ioo0s
Labels
difficulty: easy good to resolve if you know basic java and have some time to learn Upstream This issue also applies to upstream ghidra. When solving, we should better care about them.

Comments

@Escapingbug
Copy link

Escapingbug commented Jul 3, 2021 •
edited
Loading

Currently, the decompiler analyzes the function signature only inspecting itself without caring about all the call sites.

This might save the database space but the user might find this irritating as the type always not propagate cross functions.

This is also referred as "automatically commit the recognized signatures of the functions".

(Wait... the propating algorithm might also contain some problems. We might resolve it as well)
@Escapingbug Escapingbug added difficulty: easy good to resolve if you know basic java and have some time to learn Upstream This issue also applies to upstream ghidra. When solving, we should better care about them. labels Jul 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ioo0s ioo0s

Labels
difficulty: easy good to resolve if you know basic java and have some time to learn Upstream This issue also applies to upstream ghidra. When solving, we should better care about them.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Escapingbug @ioo0s