Please enable JavaScript to view this site.

Bug Validator Help

 

Waiting for a program

 

Waiting for a program is essentially the same as injection except that instead of injecting into a running program, Bug Validator watches for the process starting up and then injects.

 

noteIf the process is a service, Bug Validator won't be able to attach to it as services can't have process handles opened by third party applications, even with Administrator privileges.

 

Choose one of these methods of waiting:

 

menu File menu instructionStep Wait for Application... instructionStep shows the Wait for application wizard or dialog below

 

or click on the Wait (timer) icon on the session toolbar.

 

 toolbar-wait-for-program

 

or use the shortcut

 

 b_f2  Wait for application

 

 

Waiting for a service?

 

If your process is a service, Bug 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

 

 

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 wait for application wizard

 

The first page of the wizard lets you specify the application or choose one that you've waited for previously.

 

start-wait-wizard-application

 

 

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

 

 

Page 1: Choosing the process

 

Application to wait for instructionStep type or Browse to set the application name to launch

 

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

Image Name instructionStep shows the short program name without path

 

Reset instructionStep clears the list

 

 

Page 2: Data collection

 

Depending on your application, and what you want to validate, you may want to start collecting data as soon as injection has happened, 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 validate, obviously start collecting data from launch.

 

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

 

 

start-wait-wizard-collect

 

 

Summary and starting your program

 

The second page confirms the application and prompts you to start waiting:

 

Wait for Process... instructionStep starts waiting and then injects Bug Validator into the specified process, showing progress status

 

The button changes to show Stop Waiting. Click this to abandon the wait.

 

seeAlsoIn 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 which looks very much like the first page of the wizard above.

 

The option to start collecting data is at the top, as is the Wait For Process button

 

start-wait-dialog