Search results

Jump to: navigation, search

Create the page "Lines" on this wiki! See also the search results found.

Page title matches

  • Logging Lines
    you can write a custom probe to log the lines in function "func1" like this: // Trace all lines in fucntions
    4 KB (523 words) - 20:02, 31 May 2017

Page text matches

  • Line Probes
    You can probe source lines in your program using the '''on_line()''' directive. ...lowing expressions in an '''on_line()''' directive to indicate the line or lines:
    3 KB (451 words) - 16:58, 16 June 2017
  • Coverage data merging
    ...e three '''.bc''' files and display line counts associated with the source lines of the three Ada source files. Lines Lines
    10 KB (1,263 words) - 18:12, 8 May 2017
  • Coverage Of Null Case Alternatives
    How do I interpret lines counts from coverage on an Ada Null case alternatives? The GNAT compiler generates branches to null alternatives, as seen at lines 13 and 22 in this example:
    7 KB (715 words) - 18:44, 9 May 2017
  • Branch Coverage Cheat Sheet
    Lines with multiple branches may be easier to work with if the source code is mod Conditional operator expressions spanning multiple source lines allow for easier (not easy) determination of decisions tested.
    15 KB (2,623 words) - 22:22, 16 July 2018
  • Logging Lines
    you can write a custom probe to log the lines in function "func1" like this: // Trace all lines in fucntions
    4 KB (523 words) - 20:02, 31 May 2017
  • Brcov Predefined Probe
    ...r a particular subprogram, the details section will also list instrumented lines/branches which were not executed. The source section will annotate any prov The following are the only valid keywords that identify lines to set configuration variables. Each such line must begin with one of these
    36 KB (4,378 words) - 06:24, 20 March 2018
  • Coverage Predefined Probe
    ...s you to develop unit test cases which can be used to confirm that all the lines and branches of code you have written are executed. The reports produced b ...nstrumented, and no record will be kept of invocations of these functions, lines, or branches.
    49 KB (6,266 words) - 18:19, 7 December 2022
  • Trace Predefined Probe
    ...ay be applied to selected subprograms to log the order in which any source lines within the subprograms were executed. The probe also traces the switching f ...ines modified specified (see [[#TRACE_LINES|TRACE_LINES]]) will have their lines logged.
    22 KB (3,480 words) - 23:37, 20 March 2018
  • Info Predefined Probe
    : Prints instrumentable lines for each function symbol shown.
    3 KB (431 words) - 06:32, 20 March 2018
  • AUG Predefined Probes
    ...ne executed, so the amount of data is a constant multiple of the number of lines being covered. ...lines are those lines whose first 2 non-blank characters are "//". Comment lines are ignored by probe and are intended only for the benefit of the human rea
    17 KB (2,770 words) - 23:06, 27 February 2019
  • Call Path Profile Probe
    The following are the only valid keywords that identify lines to set configuration variables. Each such line must begin with one of these By default, if no PROBE lines exist, then coverage data will only be collected for the "main()" function
    26 KB (2,404 words) - 01:50, 22 September 2022
  • OCS Release Notes Aprobe 4.5.0 AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    17 KB (2,324 words) - 14:00, 20 December 2018
  • OCS Release Notes Aprobe 4.5.1 AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    18 KB (2,434 words) - 21:24, 25 October 2019
  • OCS Release Notes Aprobe 4.5.2 AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    18 KB (2,490 words) - 01:36, 6 March 2020
  • Memwatch Predefined Probe
    ...obe's recording to only those allocations whose call chain matches all the lines in the filter. Notice that the traceback almost always occupies several lines, and that the "==>" parts of the traceback are necessary at the beginnin
    18 KB (2,825 words) - 18:30, 6 November 2023
  • OCS Release Notes Aprobe 4.5.3 AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    19 KB (2,541 words) - 19:23, 1 February 2021
  • OCS Release Notes Aprobe 4.5.4 AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    19 KB (2,616 words) - 17:48, 13 September 2021
  • OCS Release Notes Aprobe 4.5.4a AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    19 KB (2,646 words) - 16:58, 4 October 2021
  • OCS Release Notes Aprobe 4.5.4b AIX64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    20 KB (2,666 words) - 16:55, 16 February 2022
  • Logging variables
    You can use the '''apcgen''' tool generate probes for logging functions, lines, and parameters. Version 4.4.6d of '''apcgen''' supports logging locals an
    5 KB (717 words) - 00:22, 16 August 2019
  • AUG Files Reference
    lines %boolean; lines %boolean;
    18 KB (2,871 words) - 14:44, 30 March 2020
  • AUG 5 Writing Java Probes
    ..., and exit from, the target methods. Once can also probe individual source lines of a method ''if it has been compiled with debugging information'' (usually ...g, as shown in [[#Example4.xmj|Example4.xmj]] below. Valid values for the "lines" attribute are "TRUE" or "FALSE". If you do not specify a value, "FALSE" is
    28 KB (4,074 words) - 23:02, 27 February 2019
  • AUG 1 Introduction
    * Probing the execution of any and all source lines in your program.
    5 KB (736 words) - 22:55, 27 February 2019
  • Coverage Of Null If Alternatives
    The PowerAda compiler does the same thing (see lines 12 and 21) in the same example:
    6 KB (634 words) - 20:18, 8 June 2017
  • RCUG Index
    ..._RootCause_GUI_Reference#Don't Trace All Lines In Function|Don't Trace All Lines In Function]] [[RCUG_RootCause_GUI_Reference#Trace All Lines In Function|Trace All Lines In Function]]
    41 KB (5,233 words) - 22:40, 22 March 2019
  • Porting Probe Apc Files
    ...nging, it is really that different object code is generated for the source lines by the compiler. Aprobe works from the debug line information supplied by ...<code>apcgen</code> tool to generate a dictionary of functions and source lines to help with your conversion.
    13 KB (1,885 words) - 19:03, 20 May 2020
  • OCS Release Notes Aprobe 4.5.0 Linux64
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    21 KB (2,789 words) - 13:58, 20 December 2018
  • OCS Release Notes Aprobe 4.5.1 Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    22 KB (3,033 words) - 21:22, 25 October 2019
  • OCS Release Notes Aprobe 4.5.2 Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    23 KB (3,108 words) - 01:35, 6 March 2020
  • OCS Release Notes Aprobe 4.5.3 Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    23 KB (3,151 words) - 19:21, 1 February 2021
  • OCS Release Notes Aprobe 4.5.4 Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    24 KB (3,264 words) - 17:46, 13 September 2021
  • OCS Release Notes Aprobe 4.5.4a Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,323 words) - 16:56, 4 October 2021
  • OCS Release Notes Aprobe 4.5.4b Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,348 words) - 16:53, 16 February 2022
  • OCS Release Notes Aprobe 4.5.4c Linux64
    (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,365 words) - 17:25, 8 September 2022
  • Profile Predefined Probe
    The following are the only valid keywords that identify lines to set configuration variables. Each such line must begin with one of these ...dule (including the application module) and have not specified any PROFILE lines for that module, all routines in that module will automatically be profiled
    23 KB (3,266 words) - 03:37, 22 September 2022
  • Statprof Predefined Probe
    * You can take snapshots with staprof, control the cell size, display lines and generally control things to a much finer level. ...This cells size is probably good enough to distinguish functions but not lines in the functions.
    19 KB (2,597 words) - 19:58, 7 October 2022
  • OCS Release Notes Aprobe 4.5.0 Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    44 KB (6,135 words) - 13:58, 20 December 2018
  • CallGraphProfile Predefined Probe
    The following are the only valid keywords that identify lines to set configuration variables. Each such line must begin with one of these
    12 KB (1,561 words) - 16:31, 16 July 2018
  • OCS Release Notes Aprobe 4.5.1 Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    45 KB (6,325 words) - 21:21, 25 October 2019
  • OCS Release Notes Aprobe 4.5.2 Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    46 KB (6,407 words) - 01:34, 6 March 2020
  • OCS Release Notes Aprobe 4.5.3 Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    46 KB (6,444 words) - 01:58, 2 February 2021
  • Memleak Predefined Probe
    In addition, progress lines are written to stderr, like
    10 KB (1,565 words) - 18:31, 6 November 2023
  • OCS Release Notes Aprobe 4.5.4 Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    47 KB (6,597 words) - 18:56, 13 September 2021
  • OCS Release Notes Aprobe 4.5.4ai Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    48 KB (6,635 words) - 17:14, 22 September 2021
  • OCS Release Notes Aprobe 4.5.4a Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    48 KB (6,656 words) - 16:55, 4 October 2021
  • OCS Release Notes Aprobe 4.5.4b Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    48 KB (6,681 words) - 16:52, 16 February 2022
  • OCS Release Notes Aprobe 4.5.4c Linux32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    48 KB (6,698 words) - 17:26, 8 September 2022
  • OCS Release Notes Aprobe 4.5.0 AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    60 KB (8,488 words) - 13:59, 20 December 2018
  • Memstat Predefined Probe
    // on the lines following the AllocPoint directive. The tracebacks have ...with a given traceback, and the traceback itself has to be provided on the lines following the AllocPoint directive. The tracebacks have to start with keyw
    32 KB (4,610 words) - 18:11, 3 February 2023
  • OCS Release Notes Aprobe 4.5.1 AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    61 KB (8,594 words) - 21:23, 25 October 2019
  • OCS Release Notes Aprobe 4.5.2 AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    61 KB (8,649 words) - 01:35, 6 March 2020
  • OCS Release Notes PowerAda 5.8c8 AIX32
    2220 compiler silently dumps core if Ada src has 1 million lines 2119 limit of 32767 lines per source file
    33 KB (4,506 words) - 02:37, 14 March 2019
  • OCS Release Notes Aprobe 4.5.3 AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    62 KB (8,700 words) - 19:22, 1 February 2021
  • OCS Release Notes Aprobe 4.5.4 AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    62 KB (8,772 words) - 17:47, 13 September 2021
  • OCS Release Notes Aprobe 4.5.4ai AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    62 KB (8,792 words) - 17:02, 22 September 2021
  • OCS Release Notes Aprobe 4.5.4a AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    62 KB (8,800 words) - 16:57, 4 October 2021
  • OCS Release Notes PowerAda 5.8c9 AIX32
    2220 compiler silently dumps core if Ada src has 1 million lines 2119 limit of 32767 lines per source file
    34 KB (4,594 words) - 17:21, 28 May 2020
  • OCS Release Notes Aprobe 4.5.4b AIX32
    (2492) axdln doesn't tolerate # lines (2449) brcov doesn't handle lines from multiple files
    63 KB (8,818 words) - 16:54, 16 February 2022
  • OCS Release Notes PowerAda 5.8d1 LinuxIa32
    2220 compiler silently dumps core if Ada src has 1 million lines 2119 limit of 32767 lines per source file
    34 KB (4,606 words) - 16:44, 15 September 2021
  • OCS Release Notes PowerAda 5.8d1 AIX32
    2220 compiler silently dumps core if Ada src has 1 million lines 2119 limit of 32767 lines per source file
    34 KB (4,606 words) - 23:13, 17 September 2020
  • OCS Release Notes PowerAda 5.8c7 AIX32
    2220 compiler silently dumps core if Ada src has 1 million lines 2119 limit of 32767 lines per source file
    34 KB (4,702 words) - 21:24, 5 February 2019
  • RCUG RootCause GUI Reference
    <H4> Trace All Lines in Function</H4> Use <EM>Trace All Lines In Function</EM> to add a trace for all the lines in the selected function node.
    120 KB (21,077 words) - 19:32, 22 March 2019
  • OCS Release Notes PowerAda 5.8b LinuxIa32
    2119 limit of 32767 lines per source file lines from 32767 to 65534. On Linux, line numbers greater than
    33 KB (4,506 words) - 21:38, 13 October 2020
  • RCUG 6 Deploying The RootCause Workspace
    ...the traces will be run. This is a requirement if you wish to trace source lines or access local data values. So, to be assured of reliable traces regardles
    21 KB (3,285 words) - 15:29, 20 June 2018
  • AUG Aprobe API Reference
    ...betical access to these names. This Appendix is organized along functional lines, as is the file '''aprobe.h''' itself, although the ordering is different. ...the executable and its component object files to identify to which source lines particular addresses relate. For each 'line' that Aprobe sees within a give
    102 KB (15,018 words) - 23:05, 27 February 2019
  • AUG Tools Reference
    : Verbose; echo tool command-lines and display progress messages. ...parameters on_exit<br />'''deref''' dereference pointer parameters<br />'''lines''' generate an on_line action for each source line<br />'''cast''' cast pa
    54 KB (8,176 words) - 22:19, 26 April 2022
  • RootCause FAQ
    ...ram with symbols can be probed. For "full support" (for referencing source lines and variable names and handling exceptions) you must use one of the compile ...s me for a single-line license key, but the one I have consists of several lines; do I just paste it in there? ====
    73 KB (12,088 words) - 21:47, 9 May 2017
  • AUG Index
    [[AUG_Aprobe_API_Reference#Line Iterator|for lines]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • AUG 3 Writing APC Probes
    ...ll generally give an error message explaining this. You can determine what lines may be probed, as well as which line is the first and last, by using apcgen Aprobe includes some macros for easily recording execution of entry, exit and lines: '''ap_LogSubprogramEntry''', '''ap_LogSubprogramExit''', and '''ap_LogLine
    74 KB (11,935 words) - 00:41, 11 March 2020
  • Aprobe FAQ
    (b) references to specific source lines; where mygrep.args might contain the lines:
    162 KB (25,627 words) - 17:12, 20 September 2021
Retrieved from "https://www.ocsystems.com/w/index.php/Special:Search"