Search results

Jump to: navigation, search
  • Subprogram Name Calls Lines Probed Executed Percent For 3 calls to subprogram: extern:"pkg.td.body_elab" in main3.exe
    10 KB (1,263 words) - 18:12, 8 May 2017
  • ...am. The probe records the number of calls made to functions, the number of calls made ''by'' functions. The profiling information is reported for the progr // see who calls and is called by system functions
    12 KB (1,561 words) - 16:31, 16 July 2018
  • ...narrow down the results, you would add a <code>Trigger</code> so that only calls from within a particular driver routine were traced:
    2 KB (351 words) - 15:42, 15 March 2017
  • ...anced_Topics#Nested Probes and Recursive Calls|Nested Probes and Recursive Calls]]
    8 KB (1,047 words) - 17:39, 28 February 2019
  • ...e in memory in a circular buffer. Either way, you can log many millions of calls, and you can analyze the data after the application has completed using [[A // We want to see OpenCallback and a few things it calls:
    22 KB (3,480 words) - 23:37, 20 March 2018
  • ...structures at that point so that a core dump may occur on subsequent abort calls. A fix is targeted for Aprobe version 4.4.6d. It is also possible to rebu
    2 KB (363 words) - 18:03, 3 April 2017
  • // Unfortuanately, when that time comes the first malloc() calls will cause tracebacks to be obtained
    3 KB (462 words) - 01:28, 9 March 2017
  • ...n, and the amount of time spent in each function plus all the functions it calls. The profiling information is reported for each thread and for the program ...calls. If triggers are nested (e.g. we have a trigger on Routine1() which calls Routine2() which we also have a trigger on), the levels setting for the inn
    23 KB (3,262 words) - 20:20, 4 June 2018
  • ...ests for allocations and deallocations of dynamic storage are made through calls to discrete run-time heap manager functions (e.g., malloc, free, etc.). You can control the behavior of the memcheck probe by calls from within their own probes. The API for the memcheck probe is defined by
    6 KB (944 words) - 22:44, 14 August 2019
  • ...d into a program at compilation time or link time, both the probes and the calls to them are patched into the executable program when the program is loaded ...ssor that will automatically generate the correct C code and the necessary calls to the [[AUG_Aprobe_API|Aprobe API]] from your probes. The preprocessor is
    20 KB (3,230 words) - 17:29, 22 October 2019
  • ...of the demo we illustrate the use of Predefined UALs and tracing function calls; then we'll return to the Trace Setup Dialog to add some probes. Custom pr <LI>Notice the effects of removing these calls in the next trace we generate.
    29 KB (4,850 words) - 17:20, 19 June 2018
  • ...AIX PowerAda compiler represents Ada character string values in subprogram calls and function returns [[Category:Calls]]
    10 KB (1,336 words) - 17:41, 20 February 2019
  • ...n is allocated once for each such function call. This means that recursive calls to the target function of a function probe cause multiple activations, incl ...robe. See [[#Nested Probes and Recursive Calls|Nested Probes and Recursive Calls]] below for discussion of the practical aspects of this state.
    39 KB (6,256 words) - 23:00, 27 February 2019
  • [[AUG_3_Writing_APC_Probes#C++ Class Method Calls|calling]] [[AUG_4_Advanced_Topics#Nested Probes and Recursive Calls|and recursion]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • * by providing your own probe which explicitly calls functions exported from the predefined probe. ...ick_gui.ual</code> is a library, so all interaction with it is by function calls from within a user-written probe. The statprof.ual predefined is another si
    17 KB (2,770 words) - 23:06, 27 February 2019
  • Users can control the behavior of the coverage probe by calls from within their own probes. The API for the trace probe is defined by [.. ...n file, so the run-time overhead is directly proportional to the number of calls to the functions selected and the number of branches executed in each funct
    36 KB (4,378 words) - 06:24, 20 March 2018
  • Users can control the behavior of the coverage probe by calls from within their own probes. The API for the trace probe is defined by [.. ...n file, so the run-time overhead is directly proportional to the number of calls to the functions selected and the number of lines executed in each function
    48 KB (6,141 words) - 19:47, 22 January 2019
  • Users can control the behavior of the statprof probe by calls from within their own probes. The API is defined by <code>$APROBE/include/s Calls To | Individual Time |
    19 KB (2,590 words) - 00:51, 26 November 2019
  • ...ests for allocations and deallocations of dynamic storage are made through calls to discrete run-time heap manager functions (e.g., malloc, free, etc.). You can control the behavior of the memwatch probe by calls from within their own probes. The API for the memwatch probe is defined by
    18 KB (2,766 words) - 19:04, 20 February 2019
  • .... Each Aprobe directive in your probe source causes various expansions and calls to Aprobe runtime routines. ==== C++ Class Method Calls ====
    74 KB (11,935 words) - 00:41, 11 March 2020

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