Search results

Create the page "Trace" on this wiki! See also the search results found.

Page title matches

Trace Predefined Probe
== Trace Probe: trace.ual == The '''trace.ual''' predefined probe traces the execution of selected subprograms within

22 KB (3,480 words) - 23:37, 20 March 2018

Page text matches

Finding A Symbol Using trace.ual
[[Category:Trace]] ...which function your test driver ends up calling. You could build a simple trace configuration file to report on every call to a function with "open" in its

2 KB (351 words) - 15:42, 15 March 2017
Logging Lines
You can use Aprobe to trace the execution of all or part of your program down to the line level. There * the trace predefined probe

4 KB (523 words) - 20:02, 31 May 2017
RCUG 0 Contents
: [[RCUG_5_RootCause_Demo#HEADING8-42|Define the Trace]] : [[RCUG_5_RootCause_Demo#HEADING8-65|Trace With RootCause]]

9 KB (1,118 words) - 21:35, 4 March 2018
RCUG 4 Getting Started
...bove command instead of just "my_app_driver" to allow RootCause to log and trace your application. See and the [[RCUG_RootCause_GUI_Reference#Trace_Display|Trace Display]] showing the contents of the RootCause log file.

11 KB (1,781 words) - 23:20, 17 July 2018
RCUG 5 RootCause Demo
...the whole RootCause process, showing initial definition and tuning of the trace, then collection and viewing of more detailed data about a specific functio 

29 KB (4,850 words) - 17:20, 19 June 2018
RCUG 1 Introducing RootCause
...ization as the problem report. If the support organization has defined the trace correctly, this RootCause workspace contains sufficient information to do t ...pport environments to define what to trace and also ultimately to view the trace data. The application being traced may be run in the development environmen

7 KB (1,048 words) - 23:00, 4 March 2018
Trace Predefined Probe
== Trace Probe: trace.ual == The '''trace.ual''' predefined probe traces the execution of selected subprograms within

22 KB (3,480 words) - 23:37, 20 March 2018
RCUG Index
[[RCUG_RootCause_GUI_Reference#Application|Application, in Trace Index]] ...rence#Open Associated Workspace|[3]]] [[RCUG_RootCause_GUI_Reference#Event Trace Tree|[4]]]

41 KB (5,233 words) - 22:40, 22 March 2019
RCUG 6 Deploying The RootCause Workspace
...s to the remote RootCause Agent and get back files that contain the logged trace data. ...pplication that contains debug and symbol information and then to run that trace against a version of the same application from which this debug information

21 KB (3,285 words) - 15:29, 20 June 2018
AUG Predefined Probes
...we'll refer to these by their simple filename: coverage, events, profile, trace, memwatch, etc. ...figuration file. If data is logged directly to an APD file on disk (as the trace probe can do), this may be millions of bytes of I/O being written. If data

17 KB (2,770 words) - 23:06, 27 February 2019
AUG Index
[[Trace_Predefined_Probe#Trace_Configuration_Probe|Trace Probe]] [[Trace_Predefined_Probe|ACTION, in trace.cfg]]

34 KB (4,340 words) - 23:07, 27 February 2019
RCUG 3 Terminology and Concepts
...s the component that performs the actual runtime tracing and generates the trace data. ...erred to the remote computer for use by the RootCause Agent there, and the trace data can be transferred back to the RootCause Console for examination.

43 KB (6,767 words) - 22:29, 17 July 2018
RCUG 7 Selected Topics
...raced functions and methods. For Java, RootCause inserts byte code to only trace the methods of interest, not all methods. ...roducing high trace overhead. Such functions can then be removed from the trace specification by the user in the next run. Using this mechanism and by adj

34 KB (5,685 words) - 19:44, 23 November 2017
Profile Predefined Probe
...ed by the profile probe (and the trace probe, see [[Trace_Predefined_Probe|trace.ual]]) may be greatly reduced by using the TRIGGER keyword to name a ''trig ...trigger. This is essentially an "inverse trigger", which turns profile or trace ''off'' at a given call nesting level relative to the trigger function.

23 KB (3,266 words) - 03:37, 22 September 2022
RCUG RootCause GUI Reference
...tion of user action libraries (UALs) is displayed under the UALs node. The trace predefined UAL is always present, and other predefined UALs are displayed d ...#MARKER-9-1837|Program Information Pane]] of the [[#MARKER-9-1725|Trace Display]] window.

120 KB (21,077 words) - 19:32, 22 March 2019
AUG 5 Writing Java Probes
...Some of that support is included in Aprobe in the [[Trace_Predefined_Probe|trace.ual]] predefined probe. To use this on your Java application, you would: # Copy <code>$APROBE/probes/trace.cfg</code> to <code>java.trace.cfg</code> in your current directory.

28 KB (4,074 words) - 23:02, 27 February 2019
RCUG 2 Installing RootCause
...the component that performs the actual run-time tracing and generates the trace data. ...any and all remote computers if you wish to develop probes and view their trace data locally on the remote computers.

19 KB (3,071 words) - 22:21, 4 August 2020
RCUG RootCause Files and Environment Variables
...formation about the target program configuration, the configuration of the trace setup, and the resulting log files. ...the RootCause GUI. It contains all the information needed by RootCause to trace a (possibly [[RCUG_3_Terminology_and_Concepts#MARKER-9-468|stripped]]) prog

28 KB (4,452 words) - 03:18, 26 June 2018
RCUG RootCause Command Reference
...o the result workspace before the result workspace can be used to trace an application. ...ODE> .class</CODE> or <CODE>.jar</CODE> file the workspace will be used to trace (as on the [[#MARKER-9-2101|rootcause open]] command).

35 KB (5,665 words) - 00:12, 13 January 2018
AUG 0 Contents
: [[Trace_Predefined_Probe|Trace Probe: trace.ual]]

8 KB (1,047 words) - 17:39, 28 February 2019