Profiling a Windows Service with Error Detection

Profiling a Windows Service with Error Detection

Problem:

Typically you will begin a DevPartner Error Detection (or BoundsChecker) session by selecting the  executable containing the entry point of the application, via a main method, and invoking it under Error Detection.  However, a service is called by another application and is not directly launched as an exectable with a main method would be launched.

Resolution:

 

The standalone version of DevPartner Error Detection or BoundsChecker has a feature called “Wait for Process”.  Wait for Process is an optional start up feature.  By pointing BoundsChecker to your service and issuing a “Wait for Process”, BoundsChecker will inject the binary and catch it at start up when launched from either the Service Control Manager, Net Start, or SC Start.

To utilize this feature please follow the outlined steps below:

1. (As an Administrator) Launch Error Detection(BoundsChecker) standalone:  Start > Programs >Micro Focus > DevPartner>Error Detection

2. Menu: File > Open > (Locate your Service)

3. Menu: Program > Wait For Process

4. Start your service from the SCM, Net Start, or SC Start

*Note: If the wait for process dialog box disappeared Bounds Checker has successfully injected the process and profiling has begun.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2015-05-21 13:55
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.