[Collapse]AQtrace/viewarticle/2330/
 [Expand]Introduction/viewarticle/2330/
 [Collapse]Getting Started With AQtrace/viewarticle/2420/
   AQtrace - Basic Concepts/viewarticle/2302/
   Getting Started - Requirements/viewarticle/2435/
   Planning Components Configuration and Installing AQtrace/viewarticle/2327/
  [Expand]Compiling Applications for AQtrace/viewarticle/2366/
   Adding AQtrace Reporter to Your Application/viewarticle/2333/
   Placing Modules to Build Storage/viewarticle/2369/
  [Expand]Preparing Server-Side Components/viewarticle/2404/
   Running Sample Application and Generating Dumps/viewarticle/2424/
  [Expand]Analyzing Received Error Reports/viewarticle/2383/
   Getting Started With AQtrace - What's Next?/viewarticle/2443/
 [Expand]Using AQtrace/viewarticle/2295/
 [Expand]Technical Support and Resources
 [Expand]Samples
Updated: 2/28/2013 Applies To: AQtrace 1 Rating: No votes Click to rate: PoorNot badAverageGoodExcellent
Getting Started

Placing Modules to Build Storage

« Prev     Next »     

After compiling your application and building the installation, you should place the binary files and debug information of your modules in the build storage.

The build storage is just a folder that contains the compiled modules and debug information files. The modules and debug information is needed by AQtrace Service and AQtrace Viewer to analyze the received error reports. Without these files, the Service and Viewer will not be able to parse the call stack data properly. The reports do not contain the binary code of application modules, so the Service (or Viewer) retrieves the binary code from the build storage. The presence of modules in the build storage and knowing the build storage path are critical for AQtrace Service and Viewer.

Your customers may use different versions of your application (ver. 1.0, 1.1, 2.10 and so on), so most likely you will receive error reports that were generated for different versions. The storage must contain the modules for all versions that are shipped to end-users.

Also, you should place all the modules that are included in the installation, to the build storage. For instance, if your application uses a DLL, add both the executable and the DLL.

To search for a module in the build storage, AQtrace Service and AQtrace Viewer use the module’s file name (file name and extension) and the version number.

You use the AQtrace Module Store utility to create a configuration file that contains information about the file names, the modules’ versions and their location in the storage (see below). You can then specify the file’s name and path to AQtrace Service and AQtrace Viewer and they use the information included in the file to find the needed module.

Now, let’s create the build storage and the configuration file for our sample application:

  • Launch Windows Explorer.

  • Create a new C:\Builds folder.

  • Open this folder in the Windows Explorer.

  • Create a new ver. 1.0.0 subfolder in this folder.

  • Copy compiled binary modules and debug information files to the C:\Builds\ver. 1.0.0 folder. For instance, for our sample Visual C++ application, copy the SampleApp.exe, SampleApp.pdb, SampleDll.dll and SampleDll.pdb files:

    Storage Folder
Note: We copied the debug information files (*.pdb) along with the appropriate binary modules. When searching for a module in the build storage, AQtrace Service and Viewer assumes that debug information is either included in the executables or that the debug information files reside in the same folder, in which the appropriate .exe or .dll module is located.

Now we should create the configuration file for the storage:

  • Launch the AQtrace Module Store utility. It is located in the <AQtrace>\Bin folder.

  • In the utility, select File | New from the main menu to create a new configuration file.

  • To add information about modules to the file:

    • Select Edit | Add Folder (Recursive) from the main menu. This will invoke the standard Browse for Folder dialog.

    • In the dialog, choose the C:\Builds folder and click OK.

      AQtrace Module Store will scan the C:\Builds folder and its subfolders and save information about all of the found binary modules (.exe, dll, .ocx, .bpl and so on) to the configuration file.

      Modules in the AQtrace Module Store window
  • After you added information to the configuration file, select File | Save to save the changes. Since we created a new file, it has no name, so the utility will display the standard Save File dialog to let you specify the file’s name. Save the file as C:\Builds\Config.xml. During the AQtrace installation we specified that we would use this file (see Planning Components Configuration and Installing AQtrace).

Note: You should update the build storage and configuration file for each build shipped to end-users. Otherwise, AQtrace Service and Viewer will not be able to parse the received error reports.

Adding AQtrace Reporter to Your Application     Preparing Server-Side Components

See also
Getting Started With AQtrace | Organizing Build Storage


© 2014 SmartBear Software. All rights reserved.
Email Send feedback on this document