Search results
Create the page "UAL" on this wiki! See also the search results found.
- * exporting a data from one UAL to another * using the Aprobe UAL data API4 KB (604 words) - 17:12, 10 January 2018
- == Info Probe: info.ual == The '''info.ual''' predefined probe provides the user with the general information availabl3 KB (431 words) - 06:32, 20 March 2018
- == Heap Memory Tracker Probe: hmtb.ual == The '''hmtb.ual''' predefined probe tracks the use of heap memory within an application pro5 KB (563 words) - 19:08, 16 November 2023
- : [[AUG_4_Advanced_Topics#Parameters to a UAL|Parameters to a UAL]] : [[AUG_Files_Reference#UAL file|UAL file]]8 KB (1,047 words) - 17:39, 28 February 2019
- == LogMemory Probe: logmemory.ual == The '''logmemory.ual''' predefined probe is useful for logging chunks of memory for display at f804 bytes (121 words) - 17:47, 8 April 2021
- == Memory Corruption Check Probe: memcheck.ual == The '''memcheck.ual;''' predefined probe is useful for tracking down memory corruption in an6 KB (972 words) - 18:31, 6 November 2023
- == Demand Action: demand.ual == The predefined probe demand.ual is part of a framework for "demanding" action from another probe from the c8 KB (1,203 words) - 18:05, 7 February 2019
- : [[RCUG_RootCause_Files_and_Environment_Variables#HEADING10-5|UAL File]] : [[RCUG_RootCause_GUI_Reference#HEADING11-147|Add UAL Dialog]]9 KB (1,118 words) - 21:35, 4 March 2018
- [[RCUG_RootCause_GUI_Reference#Add UAL|Add UAL]] [[RCUG_RootCause_GUI_Reference#Add Ual Dialog|Add Ual Dialog]]41 KB (5,233 words) - 22:40, 22 March 2019
- == Call Graph Profile Probe: apcgp.ual == The '''apcgp.ual''' predefined probe profiles the execution of functions within an applicati12 KB (1,561 words) - 16:31, 16 July 2018
- == Call Path Profile Probe: callpp.ual == The '''callpp.ual''' predefined probe is useful for tracking the performance of calls based o26 KB (2,404 words) - 01:50, 22 September 2022
- ...ntaining Aprobe preprocessor directives, to produce a User Action Library (UAL). The [[AUG_Tools_Reference#aprobe|aprobe]] command loads the executable i Compile the APC code. This will produce a UAL (User Action Library) that can be applied to the <code>fib</code> executabl20 KB (3,230 words) - 17:29, 22 October 2019
- == UAL File == <!-- <H2> UAL File</H2> -->28 KB (4,452 words) - 03:18, 26 June 2018
- == Memory Operations Tracker Probe: memoptb.ual == The '''memoptb.ual''' predefined probe tracks the use of memory operations (move, compare, set14 KB (1,537 words) - 18:32, 6 November 2023
- ...then be used in combination with previously-generated probes ([[#UAL File| UAL file]]s) to probe a stripped program. ...the Aprobe shared library and other object code, to produce a [[#UAL File|UAL file]].18 KB (2,871 words) - 14:44, 30 March 2020
- ...n such a probe that all the start-up actions for a predefined probe occur: UAL command-line arguments are read; the configuration file is read and recorde * by passing parameters to the UAL on the aprobe command line;17 KB (2,770 words) - 23:06, 27 February 2019
- == Performance Probe: events.ual == ''''''The '''events.ual''' predefined probe records the start and end times of program functions an18 KB (2,740 words) - 19:07, 7 October 2022
- ...is targeted for Aprobe version 4.4.6d. It is also possible to rebuild the UAL locally to correct the problem.2 KB (363 words) - 18:03, 3 April 2017
- [[AUG_4_Advanced_Topics#Parameters to a UAL|arguments for UAL]] [[AUG_2_Aprobe_Basics#Compile Probe into UAL|used by apc]]34 KB (4,340 words) - 23:07, 27 February 2019
- == Heap Memory Profile Probe: hmp.ual == The '''hmp.ual''' predefined probe profiles the use of heap memory within an application p21 KB (1,708 words) - 20:28, 27 April 2021
- == Memory Watch Probe: memwatch.ual == The '''memwatch.ual''' predefined probe monitors and gathers data about memory usage to help yo18 KB (2,825 words) - 18:30, 6 November 2023
- <!-- <H3> Enable a UAL</H3> --> === Enable a UAL ===29 KB (4,850 words) - 17:20, 19 June 2018
- == Trace Probe: trace.ual == The '''trace.ual''' predefined probe traces the execution of selected subprograms within any22 KB (3,480 words) - 23:37, 20 March 2018
- ...that you can use '''exceptions.ual''' to log exception occurrences. This UAL will record the exception kind, name, message, and traceback.4 KB (520 words) - 12:51, 4 May 2017
- ...ting object code is written to a UAL (User Action Library) file. It is the UAL file that is used at runtime to dynamically apply your tracing probes. ...a proprietary binary format. The <CODE>apformat</CODE> command reads APD, UAL and program files and generates readable text.43 KB (6,767 words) - 22:29, 17 July 2018
- ...d probes. The most recent additions are '''memstat.ual''' and '''memwatch.ual'''. You will need to compile your custom probes by referencing memstat.ual to resolve the entry points like this:4 KB (572 words) - 16:55, 31 May 2018
- ..._Tools_Reference#apc|apc]] compiler to link [[AUG_Files_Reference#UAL File|UAL file]]s. Note that the SUN <code>ld</code> command (or a completely compati ...LIBPATH</code>) in which to search for UAL files. See [[#UAL SEARCH ORDER|"UAL SEARCH ORDER"]] for more information.54 KB (8,176 words) - 22:19, 26 April 2022
- == Profile Probe: profile.ual == The '''profile.ual''' predefined probe profiles the execution of functions within an applicati23 KB (3,266 words) - 03:37, 22 September 2022
- == Branch Coverage Predefined Probe: brcov.ual == ...overage.ual]] predefined probe. See [[Coverage_Predefined_Probe|coverage.ual]] for more information.36 KB (4,378 words) - 06:24, 20 March 2018
- ...ment all subprograms, then the user must explicitly instrument them in the UAL. This is accomplished by using a call to one of the following functions def If you use the "trace.ual" predefined probe with the <code>SaveTraceDataTo APD_FILE</code> option (wh39 KB (6,256 words) - 23:00, 27 February 2019
- == Memory Leak Probe: memleak.ual == ...cker_Probe|'''memoptb.ual''']] and [[Memwatch_Predefined_Probe|'''memwatch.ual''']].10 KB (1,565 words) - 18:31, 6 November 2023
- <LI>[[#MARKER-9-1397|Setup Menu]]: [[#MARKER-9-1401|Edit UAL]] <LI>[[#MARKER-9-1397|Setup Menu]]: [[#MARKER-9-1404|Remove UAL]]120 KB (21,077 words) - 19:32, 22 March 2019
- == Test Coverage Predefined Probe: coverage.ual == ...ned_Probe|brcov.ual]] prototype. For older versions of Aprobe '''coverage.ual''' the branch coverage features described here are not available.49 KB (6,266 words) - 18:19, 7 December 2022
- The '''memstat.ual''' predefined probe uses statistical sampling to monitor memory usage to he ...ations and deallocations, which can cause performance problems, '''memstat.ual''' will sample allocations and deallocations over a longer period of time.32 KB (4,610 words) - 18:11, 3 February 2023
- '''quick_gui.ual''' is a library of functions to provide simple Java GUI support to a user-w [[Category:UAL]]6 KB (839 words) - 06:59, 20 March 2018
- (W) "/app1/aprobeinst/fred/aprobe_sun_50/ual_lib/trace.ual": This ual is not valid for your secure application. It must be listed in the secure_a34 KB (5,685 words) - 19:44, 23 November 2017
- == Statistical Profiling: statprof.ual == The statprof.ual predefined probe uses the Unix statistical profiling functions to provide a19 KB (2,597 words) - 19:58, 7 October 2022
- ...nable the [[RCUG_RootCause_GUI_Reference#MARKER-9-1347|verify]] predefined UAL in the <EM>[[RCUG_RootCause_GUI_Reference#MARKER-9-1321|Workspace Browser]] ...used the [[RCUG_RootCause_GUI_Reference#MARKER-9-1347|verify]] predefined UAL as suggested in [[#MARKER-9-887|"Deploying A RootCause Workspace"21 KB (3,285 words) - 15:29, 20 June 2018
- this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used17 KB (2,324 words) - 14:00, 20 December 2018
- this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used18 KB (2,434 words) - 21:24, 25 October 2019
- this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used18 KB (2,490 words) - 01:36, 6 March 2020
- The coverage UAL produces two types of output:10 KB (1,263 words) - 18:12, 8 May 2017
- (2679) hmtb.ual doesn't show tracebacks this version is NOT binary-compatible, with respect to UAL files.19 KB (2,541 words) - 19:23, 1 February 2021
- this version is NOT binary-compatible, with respect to UAL files. (2679) hmtb.ual doesn't show tracebacks19 KB (2,616 words) - 17:48, 13 September 2021
- this version is NOT binary-compatible, with respect to UAL files. (2679) hmtb.ual doesn't show tracebacks19 KB (2,646 words) - 16:58, 4 October 2021
- this version is NOT binary-compatible, with respect to UAL files. (2679) hmtb.ual doesn't show tracebacks20 KB (2,666 words) - 16:55, 16 February 2022
- ...produce a shared library. We call this library a "User Action Library" or UAL. Generally you can think of this as a single compilation step, that produces a UAL from APC files. However, you could, in theory, omit step 1 and write C code74 KB (11,935 words) - 00:41, 11 March 2020
- ...entifying each UAL loaded at run-time or format time. See [[#UAL SUpport|"UAL Support"]]. ...o initialize Aprobe library if you plan to use it for something other than UAL-driven tools like aprobe and apformat. This would set '''ap_AprobeState'''102 KB (15,018 words) - 23:05, 27 February 2019
- ...verage_Predefined_Probe|coverage,ual]] (and [[Brcov_Predefined_Probe|brcov.ual]]) and the tool [[AUG_Tools_Reference#bemerge|abrmerge]]. There are sectio15 KB (2,623 words) - 22:22, 16 July 2018
- ...f that support is included in Aprobe in the [[Trace_Predefined_Probe|trace.ual]] predefined probe. To use this on your Java application, you would: You can use the -d option to specify different APD filenames and the -c UAL option to name a different configuration file, for example:28 KB (4,074 words) - 23:02, 27 February 2019