Search results

Jump to: navigation, search
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    18 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 tracebacks
    19 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 tracebacks
    19 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 tracebacks
    20 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 code
    74 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 sectio
    15 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
  • ...ou'll see the details of its implementation. This doesn't apply to X.trace.ual, which is custom for each workspace. ==== 6.5 I've got a UAL that I compiled with the apc command -- how do I get that into RootCause? =
    73 KB (12,088 words) - 21:47, 9 May 2017
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    21 KB (2,789 words) - 13:58, 20 December 2018
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    22 KB (3,033 words) - 21:22, 25 October 2019
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    23 KB (3,108 words) - 01:35, 6 March 2020
  • (2679) hmtb.ual doesn't show tracebacks this version is NOT binary-compatible, with respect to UAL files.
    23 KB (3,151 words) - 19:21, 1 February 2021
  • ...les_Reference#APC File|APC]] file(s) into a [[AUG_Files_Reference#UAL File|UAL]]. ...ding and applying patches in the specified [[AUG_Files_Reference#UAL File|UAL]](s).
    162 KB (25,627 words) - 17:12, 20 September 2021
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    44 KB (6,135 words) - 13:58, 20 December 2018
  • this version is NOT binary-compatible, with respect to UAL files. (2679) hmtb.ual doesn't show tracebacks
    24 KB (3,264 words) - 17:46, 13 September 2021
  • this version is NOT binary-compatible, with respect to UAL files. (2533) coverage.ual core dumps if -if used
    45 KB (6,325 words) - 21:21, 25 October 2019
  • this version is NOT binary-compatible, with respect to UAL files. (2679) hmtb.ual doesn't show tracebacks
    25 KB (3,323 words) - 16:56, 4 October 2021

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