WINDOWS DEVELOPER UTILITY / BY BBSOFT LLC

Version 1.6.0 · Windows x64

COMTracer

Follow the call.

See the COM methods your application calls, with available arguments, return values and stacks. Discover custom interfaces from type libraries, resolve Automation names, and optionally follow DLL function calls.

Signed installer and portable ZIP.See it in action

From interface
to method.

Attach to a running x64 process or launch it with tracing active. Inspect method calls as they arrive, filter the trace, and export JSONL for later analysis. Minimize to the system tray to keep a capture running.

02 / WHAT YOU CAN TRACE

Names, arguments
and context.

01

COM method calls

Trace observed interface methods with supported signatures, including available inputs, outputs, HRESULTs, thread IDs, timings and optional call stacks.

BEYOND COM ACTIVATION
02

Custom interfaces

Discover embedded type libraries in loaded EXEs and DLLs, import .tlb or .olb files, and browse which libraries supplied each interface and method.

DISCOVER & IMPORT
03

Automation names

Resolve IDispatch members from type information and observed name lookups. Recognized interface IDs gain friendly names from a Windows catalog and the registry.

MAKE THE TRACE READABLE
04

DLL function calls

Optionally trace regular imports, delay-loaded functions and executable exports obtained through GetProcAddress, by name or ordinal.

EXE & SELECTED CALLING DLLS
05

Focus and export

Filter by method, IID or argument value. Pause recording, follow the latest events, inspect details and save the trace as JSONL.

KEEP USEFUL CONTEXT
06

Tray and detach

Keep tracing from the system tray. Closing COMTracer removes its hooks and unloads the tracing DLL after active hook callbacks finish.

LEAVE THE HOST RUNNING

COM capture depends on observing an interface and having a supported signature. Unknown signatures can be supplied in a profile. Optional DLL function traces record entry, caller and stack information; they do not decode unknown arguments or return values.

03 / FROM THE APPLICATION

Inspect a call.
Understand its context.

COM METHOD TRACEVERSION 1.5.0 / INCLUDED DEMO
COMTracer showing IUserDefined and IUserCalculator demo calls with arguments, return values and timings
Custom interface and Automation calls from the included demo. Select the image to view it at full size.

Method details

Available inputs, output values and HRESULTs stay alongside each call.

Library provenance

See which source provided each imported interface and method.

Local inspection

The desktop utility captures and exports traces on your machine.

View the type-library browser screenshot → Both screenshots use the included demo application.

04 / DOWNLOAD

Ready for
Windows.

Current release: 1.6.0 · Windows x64

MCP setup Release notes

01 / INSTALLER

Windows

x64 · Signed MSI

Windows 10 version 1709 or newer, including Windows 11. Traces native x64 processes.

Download MSI installer

4.7 MiB COMTracer-1.6.0-x64.msi

Installs the app, MCP server, tracing DLL, demo and documentation. Signed and timestamped by BBSOFT LLC.

02 / PORTABLE

Portable

x64 · ZIP archive

Extract the full archive into a folder, then run COMTracer.exe. Keep the executable and tracing DLL together.

Download portable ZIP

1.7 MiB COMTracer-1.6.0-x64.zip

Contains the same signed app, MCP server, hook DLL and demo, plus profiles, documentation and dependency licenses.

Verify your download. Compare the package hash with SHA256SUMS.txt. Embedded Windows signatures identify the publisher as BBSOFT LLC.

Release details. Checksums, signing receipts and release notes accompany the official packages.

05 / GET STARTED

Choose a process.
Follow its calls.

Use the included demo to explore a trace before attaching to your application.

  1. 01

    Install or extract

    Run the MSI, or extract the portable ZIP and open COMTracer.exe. Select Run demo to see sample COM interfaces and Automation methods.

  2. 02

    Attach or launch

    Choose a running x64 process and select Attach, or use Launch… to capture from startup. Run COMTracer elevated when the target runs elevated.

  3. 03

    Expand the capture

    Leave Discover interfaces enabled, import .tlb/.olb files when needed, and use View… to inspect the library catalog. Enable Trace DLL imports for optional DLL function entry events; add calling DLL names under Also trace DLLs.

06 / CAPTURE SCOPE

Know what
is visible.

  1. 01

    Will every custom COM method appear?

    The tracer needs a live interface obtained through an observed discovery path and a supported method signature. Type libraries and profiles extend coverage; unavailable signatures are not guessed.

  2. 02

    What does DLL tracing cover?

    The target EXE and selected calling DLLs. Standard MSVC delay-load resolution and new GetProcAddress lookups are supported. Function pointers obtained before attachment, custom export resolvers and direct internal calls are outside this mode. Tracing changes returned function-pointer identity. The included README explains scope and cleanup details.

Connect Codex or Claude Code

The MSI and portable ZIP include a local MCP server for Windows x64. After installing the MSI, run the command for your client in PowerShell. For the ZIP, use the full path to COMTracerMCP.exe in the extracted folder.

Codex

codex mcp add comtracer -- "C:\Program Files\BBSoft LLC\COMTracer\COMTracerMCP.exe"
codex mcp list

Claude Code

claude mcp add --transport stdio --scope local comtracer -- "C:\Program Files\BBSoft LLC\COMTracer\COMTracerMCP.exe"
claude mcp list

Open a new client session, start COMTracerDemo.exe, and ask the agent to trace the demo. Confirm the target and profile in the Windows dialog. Try asking, "Read the next batch of COM events and show each method with its arguments and return value." Ask the agent to disconnect when finished.

COMTRACER / BY BBSOFT LLC

A closer look
at your application.

Questions or feedback?

Contact BBSoft LLC for COMTracer inquiries and product support.

support@bbsoftllc.com