Search results

Jump to: navigation, search
  • 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
    49 KB (6,266 words) - 18:19, 7 December 2022
  • 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,597 words) - 19:58, 7 October 2022
  • ...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,825 words) - 18:30, 6 November 2023
  • .... 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
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    17 KB (2,324 words) - 14:00, 20 December 2018
  • Note that although all this probe does is make some calls to print via <code>System.out.println()</code>, probes may contain arbitrar ....java]], on the next page, tracks the beginning of all threads, and counts calls to methods within each of those threads. The [[#Example7.xmj|Example7.xmj]]
    28 KB (4,074 words) - 23:02, 27 February 2019
  • ...''callpp.ual''' predefined probe is useful for tracking the performance of calls based on their call paths (tracebacks).
    26 KB (2,404 words) - 01:50, 22 September 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    18 KB (2,434 words) - 21:24, 25 October 2019
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    18 KB (2,490 words) - 01:36, 6 March 2020
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    19 KB (2,541 words) - 19:23, 1 February 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    19 KB (2,616 words) - 17:48, 13 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    19 KB (2,646 words) - 16:58, 4 October 2021
  • ...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 '''memstat''' probe by calls from within their own probes. The API for the '''memstat''' probe is define
    32 KB (4,610 words) - 18:11, 3 February 2023
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    20 KB (2,666 words) - 16:55, 16 February 2022
  • ...after the <code>in</code> keyword), but may also be used in Aprobe runtime calls. References to the application module generally do not need a module name.
    13 KB (1,885 words) - 19:03, 20 May 2020
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    21 KB (2,789 words) - 13:58, 20 December 2018
  • ...at a RootCause trace adds is proportional to the number of traced function calls made by the program as it's running. Often it's the case that the most-freq ...you can get even more control and power with a custom probe which directly calls the Aprobe runtime functions <CODE>ap_RootCauseTraceEnable()</CODE> and <CO
    43 KB (6,767 words) - 22:29, 17 July 2018
  • ...optimized, non-debug version of the program. However, inlining of function calls may eliminate some or all points at which the probes would be executed.
    21 KB (3,285 words) - 15:29, 20 June 2018
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    22 KB (3,033 words) - 21:22, 25 October 2019
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    33 KB (4,506 words) - 21:38, 13 October 2020
  • ...probe is running on a multiprocessor machine under AIX version 4.3, aprobe calls the system function<code> bindprocessor() </code>to map aprobe and the targ ...inux only) If defined and non-blank, Aprobe should not check for functions calls in function prologs.
    54 KB (8,176 words) - 22:19, 26 April 2022
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    33 KB (4,506 words) - 02:37, 14 March 2019
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    23 KB (3,108 words) - 01:35, 6 March 2020
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    23 KB (3,151 words) - 19:21, 1 February 2021
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    34 KB (4,594 words) - 17:21, 28 May 2020
  • Users can control the behavior of the heap memory profile probe by calls from within their own probes. The API is defined by [../include/hmp.h <code
    21 KB (1,708 words) - 20:28, 27 April 2021
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    34 KB (4,606 words) - 16:44, 15 September 2021
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    34 KB (4,606 words) - 23:13, 17 September 2020
  • 1872 ada -O calls local subp body but erases csect, so bind errors 1954 Locking_Policy calls pthread_setschedparam too often
    34 KB (4,702 words) - 21:24, 5 February 2019
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    44 KB (6,135 words) - 13:58, 20 December 2018
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    24 KB (3,264 words) - 17:46, 13 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    45 KB (6,325 words) - 21:21, 25 October 2019
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    60 KB (8,488 words) - 13:59, 20 December 2018
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    25 KB (3,323 words) - 16:56, 4 October 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    25 KB (3,348 words) - 16:53, 16 February 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    25 KB (3,365 words) - 17:25, 8 September 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    46 KB (6,407 words) - 01:34, 6 March 2020
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    61 KB (8,594 words) - 21:23, 25 October 2019
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    46 KB (6,444 words) - 01:58, 2 February 2021
  • Events identified by the calls to the hooks library are automatically recorded by the events probe. The pa
    18 KB (2,740 words) - 19:07, 7 October 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    61 KB (8,649 words) - 01:35, 6 March 2020
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    62 KB (8,700 words) - 19:22, 1 February 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    62 KB (8,772 words) - 17:47, 13 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    62 KB (8,792 words) - 17:02, 22 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    62 KB (8,800 words) - 16:57, 4 October 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    63 KB (8,818 words) - 16:54, 16 February 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    47 KB (6,597 words) - 18:56, 13 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    48 KB (6,635 words) - 17:14, 22 September 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    48 KB (6,656 words) - 16:55, 4 October 2021
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    48 KB (6,681 words) - 16:52, 16 February 2022
  • (2451) support enable/disable calls and apdemand in memstat (2375) Warn if probing system calls
    48 KB (6,698 words) - 17:26, 8 September 2022
  • <LI><CODE>gethrtime(3C) (wall time) </CODE>- calls the gethrtime() system function and displays the value returned, the elapse <LI><CODE>gethrvtime(3C) (CPU time)</CODE> - calls the gethrvtime() system function and displays the value returned, the CPU t
    120 KB (21,077 words) - 19:32, 22 March 2019
  • For instance, I have a test that calls a synchronized method from a thread's run method: Child calls (native/Java): 4190 / 0
    73 KB (12,088 words) - 21:47, 9 May 2017
  • * Rename your application and replace it with a hard-coded script that calls aprobe on the renamed executable. On Unix there is a script delivered that ...e routines one() and two() which both call routine three() which, in turn, calls routine four():
    162 KB (25,627 words) - 17:12, 20 September 2021
  • ...ine A you make a call to another routine in your application (say B) which calls routine C. You have a probe on C which you want to happen. You could bracke ...e a block of "memory" in the log file that you can write to. The following calls allow you to lock and release such an area. Be aware that not every log met
    102 KB (15,018 words) - 23:05, 27 February 2019

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