Search results

Jump to: navigation, search

Page title matches

  • ...the right linux symbol for each probe is the first change to make. If the apc compiler doesn’t find the symbol for a probe, it will cause more errors f Next, make a pass through your <code>apc</code> file looking for <code>“b]”</code>, as in <code>extern:“pkg.su
    13 KB (1,885 words) - 19:03, 20 May 2020
  • = Writing APC Probes = This chapter describes how to write probes in for native programs in APC. Probes for Java programs are written in Java, and are described in [[AUG_5
    74 KB (11,935 words) - 00:41, 11 March 2020

Page text matches

  • ...linked the XlC compiler produces debug information which allows the <code>Apc</code> compiler to correctly handle references to objects of that type, tha ...big such an object is or what its layout is. The user can give the <code>Apc</code> compiler some help in determining the complete type for an incomplet
    2 KB (270 words) - 22:22, 26 April 2022
  • === APC Source === // stub_abort.apc
    2 KB (363 words) - 18:03, 3 April 2017
  • apc -x main.exe -e flag t1.apc apc -x main.exe -o t2.ual t1.ual t2.apc
    4 KB (604 words) - 17:12, 10 January 2018
  • ; [[AUG_3_Writing_APC_Probes|CHAPTER 3 - Writing APC Probes]] : [[AUG_Tools_Reference#apc|apc]]
    8 KB (1,047 words) - 17:39, 28 February 2019
  • In general, you will use the Apc compiler to compile probes written in APC which use probe points that name symbols in your program, like:
    3 KB (432 words) - 23:14, 18 December 2017
  • apc -x my_program.exe useprobe.apc logmemory.ual
    804 bytes (121 words) - 17:47, 8 April 2021
  • Aprobe's APC language is translated to C, so strings within APC are nul-terminated C strings. But variables and parameters in the program You can easily log PowerAda strings as slices in APC. The slices are fixed length. For example, use:
    10 KB (1,336 words) - 17:41, 20 February 2019
  • apc -x my program.exe myprobe.apc cppstring.ual
    1 KB (196 words) - 00:22, 9 March 2021
  • ...nce#apc|apc]], and we refer to files containing preprocessor directives as APC files. The examples in this book generally use these preprocessor directive ...ode>probe variables</code>, which are those identifiers defined within the APC itself.
    20 KB (3,230 words) - 17:29, 22 October 2019
  • apc -x main.exe my.apc apcgen -qlines -x main.exe > mytrace.apc
    4 KB (523 words) - 20:02, 31 May 2017
  • The <code>ap_OfferDemand()</code> macro is invoked in the UAL APC files. You only need to look at the macro to write custom APC which offers
    8 KB (1,203 words) - 18:05, 7 February 2019
  • [[AUG_Tools_Reference#apc|-C apc option]] APC
    34 KB (4,340 words) - 23:07, 27 February 2019
  • == APC file == .../code>, and the file must be preprocessed by the [[AUG_Tools_Reference#apc|apc]] preprocessor, which also submits the resulting C file to your C compiler,
    18 KB (2,871 words) - 14:44, 30 March 2020
  • ...the right linux symbol for each probe is the first change to make. If the apc compiler doesn’t find the symbol for a probe, it will cause more errors f Next, make a pass through your <code>apc</code> file looking for <code>“b]”</code>, as in <code>extern:“pkg.su
    13 KB (1,885 words) - 19:03, 20 May 2020
  • : [[RCUG_RootCause_GUI_Reference#HEADING11-246|Custom Apc Files Dialog]] : [[RCUG_RootCause_GUI_Reference#HEADING11-431|Generate Custom APC Dialog]]
    9 KB (1,118 words) - 21:35, 4 March 2018
  • [[RCUG_RootCause_GUI_Reference#Add to custom apc files|Add to custom apc files]] [[RCUG_3_Terminology_and_Concepts#APC|APC]]
    41 KB (5,233 words) - 22:40, 22 March 2019
  • apcgen -qparams -p pkg.p1 -x main.exe > a.apc In the generated apc in a.apc you will see the hidden parameters for the lower and upper bounds:
    9 KB (1,262 words) - 17:41, 20 February 2019
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    17 KB (2,324 words) - 14:00, 20 December 2018
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    21 KB (2,789 words) - 13:58, 20 December 2018
  • ...contains ANSI C code interspersed with Aprobe preprocessor directives. The APC file is compiled and linked using your native C compiler, and the resulting <!-- <H4>APC</H4> -->
    43 KB (6,767 words) - 22:29, 17 July 2018
  • apc -x my_app.exe my_probe.apc memstat.ual
    4 KB (572 words) - 16:55, 31 May 2018
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    18 KB (2,434 words) - 21:24, 25 October 2019
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    18 KB (2,490 words) - 01:36, 6 March 2020
  • (2646) union field type not found in apc. (2650) Struct field references don't compile in apc
    23 KB (3,108 words) - 01:35, 6 March 2020
  • (2626) apc compile error: Expecting an operand of a numeric type RHEL8 (2630) apc parse error on slice range with Gcc 8
    22 KB (3,033 words) - 21:22, 25 October 2019
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    23 KB (3,151 words) - 19:21, 1 February 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    19 KB (2,541 words) - 19:23, 1 February 2021
  • (2733) apc compile fails on dynamic variant size versions, so you shouldn't need to change any APC files. However,
    20 KB (2,666 words) - 16:55, 16 February 2022
  • (2688) Apc compiler fails to convert class with incomplete base type versions, so you shouldn't need to change any APC files. However,
    24 KB (3,264 words) - 17:46, 13 September 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    19 KB (2,616 words) - 17:48, 13 September 2021
  • ...Probes|&quot;Writing Custom Probes&quot;]] for how to include hand-written APC in your RootCause Workspace. The RootCause Console GUI takes advantage of Aprobe's APC translator to provide function prototype information for C object modules i
    34 KB (5,685 words) - 19:44, 23 November 2017
  • (2733) apc compile fails on dynamic variant size versions, so you shouldn't need to change any APC files. However,
    25 KB (3,348 words) - 16:53, 16 February 2022
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    25 KB (3,365 words) - 17:25, 8 September 2022
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    19 KB (2,646 words) - 16:58, 4 October 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    25 KB (3,323 words) - 16:56, 4 October 2021
  • The commands [[#apc|apc]], [[#apcgen|apcgen]], [[#apinfo|apinfo]], [[#apjava|apjava]], [[#apmkadi|a ...h of the system linker that is to be used by the [[AUG_Tools_Reference#apc|apc]] compiler to link [[AUG_Files_Reference#UAL File|UAL file]]s. Note that th
    54 KB (8,176 words) - 22:19, 26 April 2022
  • ...e programs, then proceed to [[AUG_3_Writing_APC_Probes|Chapter 3, "Writing APC Probes"]] and look over the rest of this book to get a more complete idea o
    5 KB (736 words) - 22:55, 27 February 2019
  • ...line and applied to any application, without writing any APC or using the apc command. ...he snapshot. You can include this in your own probe--call it <code>mytrace.apc</code>--as follows:
    17 KB (2,770 words) - 23:06, 27 February 2019
  • # Illegal nestings of probes are rejected by [[AUG_Tools_Reference#apc|apc]] at compile time. ...ibility to their prototype declaration which may be placed anywhere in the APC file. This definition allows a subprogram interface to be used for accessin
    39 KB (6,256 words) - 23:00, 27 February 2019
  • = Writing APC Probes = This chapter describes how to write probes in for native programs in APC. Probes for Java programs are written in Java, and are described in [[AUG_5
    74 KB (11,935 words) - 00:41, 11 March 2020
  • ...s that control how Apc files are compiled and to include additional custom Apc files. <B>Note: these options do not apply to Java-only workspaces.</B> <H4> <div id=MARKER-9-1480></div>Custom APC Files</H4>
    120 KB (21,077 words) - 19:32, 22 March 2019
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    44 KB (6,135 words) - 13:58, 20 December 2018
  • (2626) apc compile error: Expecting an operand of a numeric type RHEL8 (2630) apc parse error on slice range with Gcc 8
    45 KB (6,325 words) - 21:21, 25 October 2019
  • (2646) union field type not found in apc. (2650) Struct field references don't compile in apc
    46 KB (6,407 words) - 01:34, 6 March 2020
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    46 KB (6,444 words) - 01:58, 2 February 2021
  • (2688) Apc compiler fails to convert class with incomplete base type versions, so you shouldn't need to change any APC files. However,
    47 KB (6,597 words) - 18:56, 13 September 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    48 KB (6,635 words) - 17:14, 22 September 2021
  • (2733) apc compile fails on dynamic variant size versions, so you shouldn't need to change any APC files. However,
    48 KB (6,681 words) - 16:52, 16 February 2022
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    48 KB (6,698 words) - 17:26, 8 September 2022
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    48 KB (6,656 words) - 16:55, 4 October 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    60 KB (8,488 words) - 13:59, 20 December 2018
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    61 KB (8,594 words) - 21:23, 25 October 2019
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    61 KB (8,649 words) - 01:35, 6 March 2020
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    62 KB (8,700 words) - 19:22, 1 February 2021
  • <!-- [["rcc-6.html#MARKER-9-390">APC</DIV> --> [[RCUG_3_Terminology_and_Concepts#MARKER-9-390|APC]] file.
    29 KB (4,850 words) - 17:20, 19 June 2018
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    62 KB (8,772 words) - 17:47, 13 September 2021
  • (2733) apc compile fails on dynamic variant size versions, so you shouldn't need to change any APC files. However,
    63 KB (8,818 words) - 16:54, 16 February 2022
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    62 KB (8,792 words) - 17:02, 22 September 2021
  • versions, so you shouldn't need to change any APC files. However, That means you must recompile your probes from their APC source.
    62 KB (8,800 words) - 16:57, 4 October 2021
  • 2068 apc+PA+AIX: apc size warning for 2d array 2389 AIX apc reports MP_TREE_COLLISION
    33 KB (4,506 words) - 02:37, 14 March 2019
  • 2068 apc+PA+AIX: apc size warning for 2d array 2389 AIX apc reports MP_TREE_COLLISION
    34 KB (4,594 words) - 17:21, 28 May 2020
  • 2068 apc+PA+AIX: apc size warning for 2d array 2389 AIX apc reports MP_TREE_COLLISION
    34 KB (4,606 words) - 16:44, 15 September 2021
  • 2068 apc+PA+AIX: apc size warning for 2d array 2389 AIX apc reports MP_TREE_COLLISION
    34 KB (4,606 words) - 23:13, 17 September 2020
  • 2068 apc+PA+AIX: apc size warning for 2d array 2389 AIX apc reports MP_TREE_COLLISION
    34 KB (4,702 words) - 21:24, 5 February 2019
  • You would compile your trigger probe (in <code>trigger.apc</code>) as follows: apc -g -x my_app.exe trigger.apc memoptb.ual
    14 KB (1,510 words) - 00:37, 21 November 2020
  • ...d by '''ap_InstrumentFunction '''(which includes all that are generated by APC). ...called by pointer. If in C you would write <code>&amp;Foo</code>, then in APC you would write <code>ap_FunctionPointer(ap_ApplicationModuleId(), "Foo()",
    102 KB (15,018 words) - 23:05, 27 February 2019
  • ...Tools_Reference#apcgen|apcgen]] - generates [[AUG_Files_Reference#APC File|APC]] for some or all functions in the specified object file(s) ...pc|apc]] - compiles and links the specified [[AUG_Files_Reference#APC File|APC]] file(s) into a [[AUG_Files_Reference#UAL File|UAL]].
    162 KB (25,627 words) - 17:12, 20 September 2021
  • ...lemented by generating APC source code and then compiling it with Aprobe's apc compiler, which requires a C compiler backend. ...for a file in <code> $APROBE/probes</code> with the same name and suffix ".apc" and you'll see the details of its implementation. This doesn't apply to X.
    73 KB (12,088 words) - 21:47, 9 May 2017
  • 1212 apc crash reading DI for sig-svc.b.ada 1222 apc crashes against optimized code
    33 KB (4,506 words) - 21:38, 13 October 2020
  • ...e to build your application(s). Rather it will be used just to compile the APC source code that describes the generated probes.
    19 KB (3,071 words) - 22:21, 4 August 2020
  • ...ms. You will have to compile it yourself by copying the source, <code>hmp.apc</code>, from <code>$APROBE/probes</code> to a local directory to compile it apc -v -g hmp.apc -linker “-lpthreads -lrt”
    21 KB (1,708 words) - 20:28, 27 April 2021