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
  • 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,151 words) - 19:21, 1 February 2021
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    24 KB (3,264 words) - 17:46, 13 September 2021
  • ...is a prototype feature and it must be enabled by declaring the environment variable: A target expression, then, is an expression (perhaps just a variable or functionname), denoted by a leading '''$'''. This mechanism is used to d
    74 KB (11,935 words) - 00:41, 11 March 2020
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    25 KB (3,323 words) - 16:56, 4 October 2021
  • ...ss the PowerAda library to figure out the subtype of a string parameter or variable, whether it is bounded or unbounded, and where those bounds are stored. See
    10 KB (1,336 words) - 17:41, 20 February 2019
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    25 KB (3,348 words) - 16:53, 16 February 2022
  • variable. When working with a 64-bit installation of Aprobe and RootCause, replace all uses of the APROBE environment variable with APROBE64. The
    25 KB (3,365 words) - 17:25, 8 September 2022
  • ...RootCause Agent is enabled on a per-process-group basis via an environment variable. When rootcause is "on" in your environment, RootCause will identify and op ...n extension of the Aprobe product, the setup scripts define an environment variable, APROBE, which identifies the RootCause installation directory. $APROBE is
    43 KB (6,767 words) - 22:29, 17 July 2018
  • ...function declarations, while function probe declarations may only include variable declarations. Functions declared inside of either a program probe or a thre ...ory. That area of memory may be contain a code of a function, a value of a variable or a constant. Given the symbol ID we can determine where this symbol resid
    39 KB (6,256 words) - 23:00, 27 February 2019
  • ...ymbols can be probed. For "full support" (for referencing source lines and variable names and handling exceptions) you must use one of the compilers listed for ...rt APROBE_JRE=`which java`</code><br /> That is set the global environment variable APROBE_JRE to the full path to the java command you want to use. This must
    73 KB (12,088 words) - 21:47, 9 May 2017
  • ...er, the RootCause intercept mechanism is based on the LD_AUDIT environment variable and must be managed appropriately. ...er, the audit library is in a secure location and the LD_AUDIT environment variable is appropriately set, it will be loaded by the runtime linker. The path to
    34 KB (5,685 words) - 19:44, 23 November 2017
  • ...ane will display the data items visible from that line. Log the value of a variable by checking the box next to it. ...n other than the one shipped with RootCause you may define the environment variable APROBE_JRE to point to the java program, for example:
    120 KB (21,077 words) - 19:32, 22 March 2019
  • ...h of this column is determined by the [[#EventNameLength|EventNameLength]] variable, which defaults to 30.
    18 KB (2,740 words) - 19:07, 7 October 2022
  • ...ntionally keeps it around until program completion. Without tracking every variable to which a heap address is assigned, it is impossible to know when all poin
    18 KB (2,825 words) - 18:30, 6 November 2023
  • ...bling of probes. This is called "load shedding". The LoadSheddingThreshold variable must be followed by an integer. The default is zero, indicating that load s
    22 KB (3,480 words) - 23:37, 20 March 2018
  • ...initially 5). This thread-level trigger is controlled by the configuration variable ProfilingEnabledInitially (or TracingEnabledInitially). So for a TRIGGER on
    23 KB (3,266 words) - 03:37, 22 September 2022
  • LD_AUDIT environment variable [[RCUG_RootCause_Files_and_Environment_Variables#LD_AUDIT (Solaris)|[1]]] [
    41 KB (5,233 words) - 22:40, 22 March 2019
  • ...e function when the symbol refers to a code location or the beginning of a variable, etc. ...r />'''NumItems''' - The number of items being logged.<br />Then follows a variable number of arguments. Each one is a pointer to some memory where the data to
    102 KB (15,018 words) - 23:05, 27 February 2019
  • ...If the library is moved, you can specify its location with the environment variable <code>APROBE_POWERADA_LIBRARY</code>, for example: ...the same reason. A good rule is, if the debugger can print the value of a variable x at line 15, then you can do "on_line(15) log($x)" in your probe.
    162 KB (25,627 words) - 17:12, 20 September 2021
  • 3. The installation location is defined by the environment variable
    17 KB (2,324 words) - 14:00, 20 December 2018
  • ...JDK are under the same directory, identified by the JAVA_HOME environment variable.
    28 KB (4,074 words) - 23:02, 27 February 2019
  • 3. The installation location is defined by the environment variable
    18 KB (2,434 words) - 21:24, 25 October 2019
  • 3. The installation location is defined by the environment variable
    18 KB (2,490 words) - 01:36, 6 March 2020
  • 3. The installation location is defined by the environment variable
    19 KB (2,541 words) - 19:23, 1 February 2021
  • 3. The installation location is defined by the environment variable
    19 KB (2,616 words) - 17:48, 13 September 2021
  • 3. The installation location is defined by the environment variable
    19 KB (2,646 words) - 16:58, 4 October 2021
  • ...ntionally keeps it around until program completion. Without tracking every variable to which a heap address is assigned, it is impossible to know when all poin
    32 KB (4,610 words) - 18:11, 3 February 2023
  • 3. The installation location is defined by the environment variable
    20 KB (2,666 words) - 16:55, 16 February 2022
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    60 KB (8,488 words) - 13:59, 20 December 2018
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    61 KB (8,594 words) - 21:23, 25 October 2019
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    44 KB (6,135 words) - 13:58, 20 December 2018
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    61 KB (8,649 words) - 01:35, 6 March 2020
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    62 KB (8,700 words) - 19:22, 1 February 2021
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    62 KB (8,772 words) - 17:47, 13 September 2021
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    62 KB (8,792 words) - 17:02, 22 September 2021
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    62 KB (8,800 words) - 16:57, 4 October 2021
  • 12. (1772) huge array generated for xlC 11.1 variable are wasteful of virtual memory. An environment variable
    63 KB (8,818 words) - 16:54, 16 February 2022
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    45 KB (6,325 words) - 21:21, 25 October 2019
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    46 KB (6,407 words) - 01:34, 6 March 2020
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    46 KB (6,444 words) - 01:58, 2 February 2021
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    47 KB (6,597 words) - 18:56, 13 September 2021
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    48 KB (6,635 words) - 17:14, 22 September 2021
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    48 KB (6,656 words) - 16:55, 4 October 2021
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    48 KB (6,681 words) - 16:52, 16 February 2022
  • the environment variable AP_NFS_TMP=1 before running aprobe. Aprobe (2520) Linux gcc problem reading static member variable
    48 KB (6,698 words) - 17:26, 8 September 2022