comon v2.1

Comon breakpoints are now public and shared with the main WinDbg session. You may manage them with the regular bp command (!cobl and !cobd were no longer needed).

I rewrote the !cobp command which now allows to set breakpoints and tracepoints on COM methods. When a given breakpoint is hit, comon will try to print the method parameters (if metadata was available).

!coreg evaluates memory addresses according to WinDbg parsing rules. It also saves the registed vtable in the database (you may avoid this by using the --nosave option).

Comon will show only the metadata in accordance with the bitness of the target process. In the past, the 64-bit version registered 32-bit and 64-bit COM metadata. However, it proved to raise various errors, and I decided to simplify this logic.

I added a new command, !cometa showm {module_name}, to list CLSIDs registered by a given module.

comon v2.0

Contains many changes and improvements, including:

• filtering added to the !comon attach command (-i/-e) (removed !colog command)
• removed duplicate breakpoints (logs are clearer now)
• fixed issues with filtering
• !comon status (new command) to list COM object registrations in the current debugging session
• DllGetClassObject breakpoints (removed most of the Co... breakpoints as they were not reliable)
• virtual memory protection updates for breakpoints (required for breakpoints in the COM Pre-stubs in .NET apps)
• added synthetic symbols
• removed !cobp - synthetic symbols and !comon status command should give you all the information required to set breakpoints manually
• !cobd command to remove internal breakpoint set by comon

Full Changelog: 1.1...2.0

comon v1.1

Changes:

• Added support for the CoGetInstanceFromFile and CoRegisterClassObject functions (#1)
• Virtual table addresses are now displayed also for unknown CLSIDs and IIDs
• Improved build process

Fixes:

• fixed errors when using comon with TTD

Full Changelog: 1.0...1.1-2

comon v1.0

Initial release