data-flow-tracer

Tracing data flow in decompiled binaries involves applying forward or backward traces to map parameter propagation and API argument origins. This reveals how inputs move through callees, constants, and global state interactions.

Mapping global state producers and consumers is done by using global state mapping techniques to build producer and consumer maps for global variables across a module. This tracks how variables interact throughout the code.

Yes, you can track string lineage by applying string tracing methods to decompiled code. This follows how string literals propagate and identifies who references them across functions and modules.

Yes, you need to identify the module DB with the decompiled-code-extractor before running a forward trace. This database provides the decompiled code and assembly context required to track data movement accurately.

Use forward trace to follow how a function parameter propagates into callees, and use backward trace to identify the origins of an API's arguments. Both leverage tracking databases to reveal data movement.