Search results

Jump to: navigation, search

Page title matches

  • 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

  • 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
  • ...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
  • 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
  • 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
  • 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
  • ...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
  • ...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.
    48 KB (6,141 words) - 19:47, 22 January 2019
  • ...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
  • : Prints instrumentable lines for each function symbol shown.
    3 KB (431 words) - 06:32, 20 March 2018
  • ...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
  • (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
  • (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
  • ...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,766 words) - 19:04, 20 February 2019
  • (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
  • 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
  • lines %boolean; lines %boolean;
    18 KB (2,871 words) - 14:44, 30 March 2020
  • ..., 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
  • * Probing the execution of any and all source lines in your program.
    5 KB (736 words) - 22:55, 27 February 2019
  • 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
  • ..._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

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