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

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