Search results

Jump to: navigation, search
  • ...m a probe in a scope where the variable is visible or you must specify the variable scope in the target expression. ...ables and globals within the same file using the target expression for the variable.
    5 KB (717 words) - 00:22, 16 August 2019
  • You can set this variable to the severity level at which you want to trigger Aprobe to dump core, lik You can set this variable to a string contained in the message you want to trigger Aprobe to dump cor
    1 KB (248 words) - 23:16, 3 October 2021
  • ...unted disks available, you can use the <code>AP_NFS_TMP</code> environment variable to request that Aprobe put the APD file in <code>/tmp</code> then Aprobe wi
    540 bytes (92 words) - 21:29, 28 September 2017
  • For each monitored variable in your program, call '''ap_CreateHistogram()''' to allocate an object that ...f the monitored variable. This can be done periodically, or every time the variable changes.
    6 KB (839 words) - 06:59, 20 March 2018
  • Sometimes you just want to print the value of a (complex) variable at runtime. You can do this using the logging facility of Aprobe using imm Normally you log a target program variable using the <code>log()</code> function of Aprobe, and then format the logged
    3 KB (417 words) - 18:02, 26 June 2017
  • ...e registry is defined by the [[#MARKER-9-992|APROBE_REGISTRY]] environment variable, and is generally under the [[#MARKER-9-971|.rootcause Directory]] so that ...d by the setup script. We suggest that you do not modify this environment variable.
    28 KB (4,452 words) - 03:18, 26 June 2018
  • ...include the path <code>$APROBE/lib</code> in your library path environment variable (<code>LIBPATH</code> (AIX) or <code>LD_LIBRARY_PATH</code> (Linux)) using
    2 KB (324 words) - 17:16, 22 June 2018
  • Function sacrificing can be disabled by setting the environment variable <code>APROBE_DISABLE_SACRIFICE=TRUE</code>. This should only be used if pr ...e the search for patch areas in you application by setting the environment variable: <code>APROBE_DISABLE_PATCHAREA=TRUE</code>.
    5 KB (795 words) - 20:32, 13 June 2019
  • [[AUG_Tools_Reference#APC_LD_COMMAND|APC_LD_COMMAND environment variable]] [[AUG_Tools_Reference#APROBE|APROBE environment variable]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • ...riable and appends <CODE>$APROBE/bin</CODE> to your '''PATH''' environment variable. It also sets defaults for both '''APROBE_REGISTRY''' and '''APROBE_LOG'''
    11 KB (1,781 words) - 23:20, 17 July 2018
  • probe_variable_decl ::= &lt;C variable declaration&gt; ...ion on the <code>aprobe</code> command, or else by setting the environment variable APROBE_RING_SIZE.
    18 KB (2,871 words) - 14:44, 30 March 2020
  • ...s</B> option, in order for RootCause and Aprobe to resolve source line and variable references. ...s</B> option, in order for RootCause and Aprobe to resolve source line and variable references.
    19 KB (3,071 words) - 22:21, 4 August 2020
  • ...All options are specified using the <code>MALLOCOPTIONS</code> environment variable.
    5 KB (796 words) - 14:38, 17 September 2020
  • ...pe target expression. The syntax for specifying the scope of an Ada static variable differs between PowerAda and Gnat. is used to reference the variable <code>x</code> in the body of the unit named <code>unit</code>.
    13 KB (1,885 words) - 19:03, 20 May 2020
  • ...ams just as to C and C programs. However, Ada requires special handling of variable names, scoping and exceptions, for which Aprobe provides explicit syntax an ...ibCalls</code> (a variable in the probe) and <code>NumIterations</code> (a variable in the program being probed), and it logs the right amount of data and how
    20 KB (3,230 words) - 17:29, 22 October 2019
  • ...uot;Getting Started&quot;]]. This will define the '''APROBE''' environment variable which is necessary to use RootCause. Lastly, make sure your '''DISPLAY''' environment variable is set. If you're using a Windows client that is running X emulator softwa
    29 KB (4,850 words) - 17:20, 19 June 2018
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    21 KB (2,789 words) - 13:58, 20 December 2018
  • ...code>$APROBE/bin</code> must also be in your <code>PATH</code> environment variable. ...he target program process to processor 0. If the value of this environment variable is defined to a value of 1 or greater, this is interpreted as a processor n
    54 KB (8,176 words) - 22:19, 26 April 2022
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    22 KB (3,033 words) - 21:22, 25 October 2019
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    23 KB (3,108 words) - 01:35, 6 March 2020

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