I’m in search of a utility that can keep track of both network operations (or at least HTTP requests) and Windows API interactions for an executable file. The application should work with a Delphi-based executable for which source code isn’t available. Any recommendations for such monitoring software would be greatly appreciated.
During a similar investigation, I faced the challenge of monitoring a Delphi-based executable without source code. I opted for Sysinternals Process Monitor to track low-level file, registry, and system calls, which offered valuable insights into what was happening internally. For the network aspect, Wireshark proved indispensable by capturing all the traffic, even if it sometimes required piecing together the request context manually. Although combining data from these two tools was less straightforward than using a single integrated solution, it ultimately provided a comprehensive view of both network and device-level activities.
I encountered a similar challenge while troubleshooting a proprietary executable. I found success by using a combination of Process Hacker and a dedicated HTTP debug proxy. Process Hacker proved valuable by showing real-time process details and highlighting system calls without adding too much overhead. Meanwhile, the HTTP proxy allowed me to capture and interpret web traffic in a clear timeline, which was especially useful when the executable’s internal workings were opaque. This combination enabled me to correlate network events with underlying system operations effectively, streamlining the diagnostic process.
In a recent project, I had to monitor an executable without source access. I ended up using a dual approach where one tool handled web traffic while another provided insight into system API calls. For HTTP requests, a tool similar to Fiddler proved very useful, while software like API Monitor offered detailed tracking of Windows API interactions. Although setting up API Monitor required careful configuration, the detailed data it provided was essential in understanding how the executable communicated internally and externally. The combined method helped isolate issues effectively, and I found it added significant value to the debugging process.
i gave a try to a combo of a sniffer tool and a low-overhead api logger. sure, its not as detailed as some big names but it worked decently for my delphi exe. worth a shot if you cant use the heavier tools