Search results
Create the page "Trace" on this wiki! See also the search results found.
Page title matches
- == Trace Probe: trace.ual == The '''trace.ual''' predefined probe traces the execution of selected subprograms within22 KB (3,480 words) - 23:37, 20 March 2018
Page text matches
- [[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 its2 KB (351 words) - 15:42, 15 March 2017
- You can use Aprobe to trace the execution of all or part of your program down to the line level. There * the trace predefined probe4 KB (523 words) - 20:02, 31 May 2017
- : [[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
- ...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
- ...the whole RootCause process, showing initial definition and tuning of the trace, then collection and viewing of more detailed data about a specific functio <!-- [["rcc-11.html#MARKER-9-1725">Trace Display</DIV> -->29 KB (4,850 words) - 17:20, 19 June 2018
- ...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 environmen7 KB (1,048 words) - 23:00, 4 March 2018
- == Trace Probe: trace.ual == The '''trace.ual''' predefined probe traces the execution of selected subprograms within22 KB (3,480 words) - 23:37, 20 March 2018
- [[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
- ...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 information21 KB (3,285 words) - 15:29, 20 June 2018
- ...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 data17 KB (2,770 words) - 23:06, 27 February 2019
- [[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
- ...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
- ...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 adj34 KB (5,685 words) - 19:44, 23 November 2017
- ...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
- ...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]]</EM> of the <EM>[[#MARKER-9-1725|Trace Display]]</EM> window.120 KB (21,077 words) - 19:32, 22 March 2019
- ...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
- ...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
- ...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]]) prog28 KB (4,452 words) - 03:18, 26 June 2018
- ...o the <EM>result</EM> 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
- : [[Trace_Predefined_Probe|Trace Probe: trace.ual]]8 KB (1,047 words) - 17:39, 28 February 2019
- ...thout a C compiler. However, the only thing you can do with native code is trace it; you can't dump parameters or variables or generate probes (e.g., SNAPSH ==== 1.12 Do I need to build the program with debug to trace it? ====73 KB (12,088 words) - 21:47, 9 May 2017
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe17 KB (2,324 words) - 14:00, 20 December 2018
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe18 KB (2,434 words) - 21:24, 25 October 2019
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe18 KB (2,490 words) - 01:36, 6 March 2020
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe19 KB (2,541 words) - 19:23, 1 February 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe19 KB (2,616 words) - 17:48, 13 September 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe19 KB (2,646 words) - 16:58, 4 October 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe20 KB (2,666 words) - 16:55, 16 February 2022
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications44 KB (6,135 words) - 13:58, 20 December 2018
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications45 KB (6,325 words) - 21:21, 25 October 2019
- ...y usage), profile and statprof (for program execution time profiling), and trace (for execution tracing). These probes were already compiled into UALs, and aprobe -u trace.ual -p -g fib 1020 KB (3,230 words) - 17:29, 22 October 2019
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications46 KB (6,407 words) - 01:34, 6 March 2020
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications46 KB (6,444 words) - 01:58, 2 February 2021
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications47 KB (6,597 words) - 18:56, 13 September 2021
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications48 KB (6,635 words) - 17:14, 22 September 2021
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications48 KB (6,656 words) - 16:55, 4 October 2021
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications48 KB (6,681 words) - 16:52, 16 February 2022
- 6. (2164) java aborts under RC trace 2. (1996) problems with trace.ual in PA/ada2cpp/g++ Linux applications48 KB (6,698 words) - 17:26, 8 September 2022
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe21 KB (2,789 words) - 13:58, 20 December 2018
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe22 KB (3,033 words) - 21:22, 25 October 2019
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules60 KB (8,488 words) - 13:59, 20 December 2018
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe23 KB (3,108 words) - 01:35, 6 March 2020
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules61 KB (8,594 words) - 21:23, 25 October 2019
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules61 KB (8,649 words) - 01:35, 6 March 2020
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe23 KB (3,151 words) - 19:21, 1 February 2021
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules62 KB (8,700 words) - 19:22, 1 February 2021
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules62 KB (8,772 words) - 17:47, 13 September 2021
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules62 KB (8,792 words) - 17:02, 22 September 2021
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules62 KB (8,800 words) - 16:57, 4 October 2021
- 9. (2164) java aborts under RC trace 3.(2074) AIX RC Trace Setup doesn't show lines, modules63 KB (8,818 words) - 16:54, 16 February 2022
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe24 KB (3,264 words) - 17:46, 13 September 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,323 words) - 16:56, 4 October 2021
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,348 words) - 16:53, 16 February 2022
- aprobe -u trace my32bitapp.exe ap64 aprobe -u trace my64bitapp.exe25 KB (3,365 words) - 17:25, 8 September 2022
- === Stack Trace Support === ...eback functions and macros provide an easy mechanism for obtaining a stack trace--a list showing the current routine, the routine which called that, its cal74 KB (11,935 words) - 00:41, 11 March 2020
- ...probe code itself. The predefined probes such as [[Trace_Predefined_Probe|trace.ual]] check these. Use this macro in your probe to check the global trace-enabled count:102 KB (15,018 words) - 23:05, 27 February 2019
- ...Cause and have been using the GUI, you can use the Custom... button in the Trace Setup window to generate a probe, and look at that. If that looks too daunt The RootCause Trace Setup window shows a tree of all the functions organized by module, directo162 KB (25,627 words) - 17:12, 20 September 2021
- ...the coverage probe by calls from within their own probes. The API for the trace probe is defined by [../include/coverage.h <code>$APROBE/include/brcov.h</c36 KB (4,378 words) - 06:24, 20 March 2018
- ...the coverage probe by calls from within their own probes. The API for the trace probe is defined by [../include/coverage.h <code>$APROBE/include/coverage.h49 KB (6,266 words) - 18:19, 7 December 2022
- If you use the "trace.ual" predefined probe with the <code>SaveTraceDataTo APD_FILE</code> option aprobe -u trace.ual -d /tmp/trace-fred.apd fred39 KB (6,256 words) - 23:00, 27 February 2019