الفريق العربي للهندسة العكسية
compare different execution traces of the same exe, but ran with different params - نسخة قابلة للطباعة

+- الفريق العربي للهندسة العكسية (https://www.at4re.net/f)
+-- قسم : ENGLISH FORUM (https://www.at4re.net/f/forum-6.html)
+--- قسم : General Discussion (https://www.at4re.net/f/forum-13.html)
+--- الموضوع : compare different execution traces of the same exe, but ran with different params (/thread-4721.html)

compare different execution traces of the same exe, but ran with different params - mynameismg - 25-08-2025

I'm working on analyzing how a software's behavior changes when run with different parameters. 

My goal is to compare the execution traces (e.g., function calls, memory accesses, or instruction flows) to identify differences caused by the input parameters.


Question

I want to capture the execution trace for two runs: one with param1 and another with param2. So, for example:

- sofware.exe --param1

  VS

- software.exe --param2


Ideally, I'd like to see which functions, code paths, or memory regions are accessed differently between the two runs.
I'm looking for effective techniques to:

- Compare traces to identify key differences in execution paths
- Analyze patterns in how parameter changes affect program flow

How can I compare different execution flows?


 What I tried


I tried to use [x64Dbg's tracing feature][1]. However, you cant really compare two different executions. 


I also explored [lighthouse][2] for IDA/Binary Ninja:

[صورة مرفقة: overview.gif]

However, it seems like it doesnt seem to do what I want.


  [1]: https://help.x64dbg.com/en/latest/gui/views/Trace.html
  [2]: https://github.com/gaasedelen/lighthouse

RE: compare different execution traces of the same exe, but ran with different params - Stingered - 25-08-2025

ry using IDC function 
StartDebugger
. You can pass a C-style string (e.g. 
"\x55\x89\xe5"
)for program arguments:
***********************************************
** Launch the debugger
   arguments:
        path - path to the executable file.
        args - command line arguments
        sdir - initial directory for the process
for all args: if empty, the default value from the database will be used
   returns: -1-failed, 0-cancelled by the user, 1-ok
   See the important note to the StepInto() function

long StartDebugger(string path, string args, string sdir);
docs.hex-rays.com/user-guide/debugger/debugger-tutorials/ida_scriptable_debugger1/ida_scriptable_debugger2.md