Search results

Jump to: navigation, search

Page title matches

Page text matches

  • This page is the top level of the PowerAda documentation. The PowerAda User's Guide and Ada LRM are in the old HTML format. * [http://ada.ocsystems.com User Guide]
    491 bytes (69 words) - 17:43, 28 March 2019
  • == RootCause User Guide (RCUG) == * [[File:RootCauseCppUserGuide.pdf||||Old PDF User Guide]]
    1 KB (179 words) - 00:52, 18 February 2023
  • ...cluding the <code>logmemory.h</code> header file, calling the API from the user probe, including the probe on the Aprobe command line or in an .apo file.
    804 bytes (121 words) - 17:47, 8 April 2021
  • '''RootCause User Guide''' ...em is recorded in its RootCause workspace. The RootCause Console Graphical User Interface (GUI) allows you to choose the data to be collected and to naviga
    7 KB (1,048 words) - 23:00, 4 March 2018
  • ...i.ual''' is a library of functions to provide simple Java GUI support to a user-written probe. The interface is defined in <code>$APROBE/include/quick_gui. '''ap_AskYesOrNo()''' is a simple call you can make to prompt the user before taking some action. Returns TRUE if ''Yes'', FALSE otherwise.
    6 KB (839 words) - 06:59, 20 March 2018
  • The OCS Fast Heap is a user-defined malloc replacement for AIX (see: https://www.ibm.com/support/knowl ...Heap achieves its performance gains by using pools of fixed-size blocks. User requests are completed using the closest sized block. Blocks are never mer
    5 KB (796 words) - 14:38, 17 September 2020
  • OCS PowerAda Compilation System, supplementing the PowerAda User's Guide. The user should make sure that all task stacks are given sufficient
    5 KB (705 words) - 21:15, 13 October 2020
  • ...ompiler from knowing how big such an object is or what its layout is. The user can give the <code>Apc</code> compiler some help in determining the complet
    2 KB (270 words) - 22:22, 26 April 2022
  • '''Aprobe User Guide''' ...nterfaces described in this user's guide, and could have been written by a user. As such, they demonstrate the power and flexibility of Aprobe. But make no
    17 KB (2,770 words) - 23:06, 27 February 2019
  • '''RootCause User Guide'''
    2 KB (283 words) - 21:31, 4 March 2018
  • '''RootCause User Guide''' ...ment variables (e.g. APROBE, PATH, etc.). This is typically done by each user's login script because it usually needs to be done only once per login sess
    11 KB (1,781 words) - 23:20, 17 July 2018
  • '''RootCause User Guide''' Every user of RootCause will install the '''RootCause Console''' and the '''RootCause
    19 KB (3,071 words) - 22:21, 4 August 2020
  • Aprobe User Guide [[AUG_3_Writing_APC_Probes#User-Supplied Formatting|awk]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • '''RootCause User Guide''' ...in the underlying Aprobe product, and the user can build custom UALs. As a user of RootCause, you do not need to be concerned with these files. RootCause h
    28 KB (4,452 words) - 03:18, 26 June 2018
  • '''Aprobe User Guide'''
    2 KB (318 words) - 23:14, 8 May 2017
  • A "checkpoint" is a user-defined point at which to check all The memcheck probe helps the user identify heap corruptions from overwrites by recording all allocations and
    6 KB (972 words) - 18:31, 6 November 2023
  • The '''info.ual''' predefined probe provides the user with the general information available about the program. It can be used on
    3 KB (431 words) - 06:32, 20 March 2018
  • '''RootCause User Guide''' ...of various RootCause topics that may be of interest to you, the RootCause user.
    34 KB (5,685 words) - 19:44, 23 November 2017
  • ...the ANSI C programming language. Calls to the probes are patched into the user-specified locations of the memory image of your executable program. Probes ...erms '''application''', '''target application''', '''target program''', '''user program''', '''executable''' and '''target executable''' are used interchan
    20 KB (3,230 words) - 17:29, 22 October 2019
  • ...ogram start and then use it to set or get the data value. It is up to the user to coordinate the timing between the UALs.
    4 KB (604 words) - 17:12, 10 January 2018
  • '''RootCause User Guide''' RootCause performs root cause analysis of problems at the user's site, in the production system. This chapter discusses how to run traces
    21 KB (3,285 words) - 15:29, 20 June 2018
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    17 KB (2,324 words) - 14:00, 20 December 2018
  • ...predefined probe records the start and end times of program functions and user-defined "events", organizes them by call tree, and provides several reports ...rt the IncomingMissile event. At the point at which we display this to the user we can record the end point for the IncomingMissile.
    18 KB (2,740 words) - 19:07, 7 October 2022
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    18 KB (2,434 words) - 21:24, 25 October 2019
  • Aprobe User Guide LogIdT ::= &lt;user-defined LogID, see aprobe.h&gt;
    18 KB (2,871 words) - 14:44, 30 March 2020
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    18 KB (2,490 words) - 01:36, 6 March 2020
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    19 KB (2,541 words) - 19:23, 1 February 2021
  • '''RootCause User Guide''' [[AUG_0_Contents|Aprobe user's guide]] (<code>$APROBE/Aprobe.pdf</code>).
    43 KB (6,767 words) - 22:29, 17 July 2018
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    19 KB (2,616 words) - 17:48, 13 September 2021
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    19 KB (2,646 words) - 16:58, 4 October 2021
  • RootCause User Guide and in the file "install.txt" located in the root RootCause User Guide.
    20 KB (2,666 words) - 16:55, 16 February 2022
  • ...s, and keeping a running total of total allocated memory, and allowing the user to analyze this data to determine if memory usage is appropriate. The repor : starts the Java graphical user interface (GUI) dialog upon probe startup, before running your program. Thi
    18 KB (2,825 words) - 18:30, 6 November 2023
  • '''RootCause User Guide''' [[RCUG_RootCause_GUI_Reference#user-defined|user-defined]]
    41 KB (5,233 words) - 22:40, 22 March 2019
  • Aprobe User Guide
    5 KB (736 words) - 22:55, 27 February 2019
  • '''RootCause User Guide'''
    9 KB (1,118 words) - 21:35, 4 March 2018
  • '''RootCause User Guide''' <LI>User-written custom probes as described in
    29 KB (4,850 words) - 17:20, 19 June 2018
  • Aprobe User Guide ...n <code>aprobe.h</code>. Only two of the parameters are of interest to the user:
    39 KB (6,256 words) - 23:00, 27 February 2019
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    21 KB (2,789 words) - 13:58, 20 December 2018
  • ...s, and keeping a running total of total allocated memory, and allowing the user to analyze this data to determine if memory usage is appropriate. The repor // coming from the user code are almost always legitimate problems, which
    32 KB (4,610 words) - 18:11, 3 February 2023
  • Aprobe User Guide apc - Preprocesses and compiles APC to generate a User Action Library (UAL).
    54 KB (8,176 words) - 22:19, 26 April 2022
  • ...might need are linked to produce a shared library. We call this library a "User Action Library" or UAL. ...llowing for the initialization of user data structures or even a graphical user interface. Similarly, the C code in the on_exit section of a probe format g
    74 KB (11,935 words) - 00:41, 11 March 2020
  • '''RootCause User Guide''' This chapter describes all parts of the Rootcause Console Graphical User Interface, or the "RootCause GUI" for short. It is meant to serve as a refe
    120 KB (21,077 words) - 19:32, 22 March 2019
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    22 KB (3,033 words) - 21:22, 25 October 2019
  • Several predefined UALs offer snapshots and other actions on user demand:
    8 KB (1,203 words) - 18:05, 7 February 2019
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    23 KB (3,108 words) - 01:35, 6 March 2020
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    23 KB (3,151 words) - 19:21, 1 February 2021
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    24 KB (3,264 words) - 17:46, 13 September 2021
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    25 KB (3,323 words) - 16:56, 4 October 2021
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    25 KB (3,348 words) - 16:53, 16 February 2022
  • The RootCause User Guides are available in PDF format in the files RootCause User Guide, and in the "install.txt" file located in the
    25 KB (3,365 words) - 17:25, 8 September 2022

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)