Injecting into a running program

 

Coverage Validator attaches to a running process by injecting the stub into the process so it can start collecting data.

 

Choose one of these methods of starting the injection:

 

File menu Inject... shows the Attach to Running Process wizard or dialog below

 

Or click on the Inject icon on the session toolbar.

 

 

Or use the shortcut

 

 Inject into running application

 

 

Administrator privileges

 

The following applies only if you did not start Coverage Validator in administrator mode.

 

When choosing the inject method, a restart with administrator privileges will be required to proceed.

 

 

 

Injecting into a service?

 

If your process is a service, Coverage Validator won't be able to attach to it.

 

Services can't have process handles opened by third party applications, even with Administrator privileges.

 

In order to work with services, you can use the NT service API and monitor the service

 

You may see this warning dialog when trying to inject into a service:

 

 

 

User interface mode

 

There are two interface modes used while starting a program

 

•Wizard mode guides you through the tasks in a linear fashion
 

•Dialog mode has all options contained in a single dialog
 

All the options are the same - just in slightly different places

 

In this section we'll cover the Wizard mode first and the Dialog mode later.

 

 

The attach to running process wizard

 

The first page of the wizard shows a list of running system and user processes.

 

The Arch column is not shown when running 32 bit Coverage Validator because only 32 bit processes are listed.

 

Any processes that have grayed out .Net values cannot instrument the .Net part of the application (native components will be instrumented).

 

 

 

 

Choose the process and click Next >> for the next page of the wizard.

 

 

Page 1: Choosing the process

 

•System processes / Services / User processes show any or all of services and system or user processes in the list

 

•Full path shows the full path to the process executable in the list
 

•Image Name shows the short program name without path

 

•Refresh update the list with currently running processes

 

Clicking on the headers of the list will sort them by ID or by name using the full name or short name, depending on what's displayed.

 

 

Page 2: Data collection

 

Depending on your application, and what you want to test, you may want to start collecting data as soon as injection happens, or do it later.

 

If your program has a complex start-up procedure, initialising lots of data, it may be much faster not to collect data until the program has launched.

 

If it's the startup procedure you want to test, then obviously start collecting data from launch.

 

See the section on controlling data collection for how to turn collection on and off after launch.

 

The data collection option may be disabled because of the instrumentation mode that is selected.

 

 

Currently we only support attaching to native applications and the native part of mixed mode applications.

 

 

Summary and starting your program

 

The second page confirms the process you have selected to inject into, and prompts you to attach:

 

•Attach... injects Coverage Validator into the specified process, showing progress status

 

In the general questions see Why might Inject or Launch fail? for troubleshooting launch problems.

 

 

Dialog mode

 

In Dialog mode, all the settings are in one dialog but which still looks very much like the first page of the wizard above.

 

The option to start collecting data is at the top, as is the Attach... button