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.

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

function-data-fix #22

Merged
merged 1 commit into from
May 8, 2020
Merged

function-data-fix #22

merged 1 commit into from
May 8, 2020

Conversation

ddash-ct
Copy link
Contributor

@ddash-ct ddash-ct commented May 8, 2020

When dynamically resolving APIs, was running into a situation where the resolved API was being stored in a register and the call to the resolved address invoked the register. When attempting to use function_tracing on that call address, this resulted in a RuntimeError because when the utility attempts to use FunctionSignature, it isn't obtaining a func_type_data_t, even when the operand type is adjusted to reflect an updated, appropriate type.

Updated the code to allow the call operand type to be taken into account when a function signature is pulled.

…ion signature. This provides better support for dynamically resolved function calls.
@dc3-tsd dc3-tsd merged commit 1d754a1 into dod-cyber-crime-center:master May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants