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

  • This dialog is used to specify the number of source lines to skip. Skipping does not stop within called subprograms. Enter the number of lines to skip in the text field. Press the ''Skip'' button to execute the SKIP co
    818 bytes (118 words) - 15:32, 23 April 2019
  • This dialog is used to specify the number of source lines to step. Stepping will stop within called subprograms. Enter the number of lines to step in the text field, then press the ''Step'' button to execute the ST
    822 bytes (119 words) - 15:33, 23 April 2019
  • 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
  • ...as a sequence of wide characters grouped into lines, and as a sequence of lines grouped into pages.
    1 KB (236 words) - 15:48, 29 April 2019
  • ...e the conventional value zero), as in the case of a newly opened file, new lines and new pages are only started when explicitly called for. ...aximum page length of the specified output or append file to the number of lines specified by To. The value zero for To specifies an unbounded page length.
    3 KB (470 words) - 17:14, 1 May 2019
  • 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
  • ...ally, as a sequence of characters grouped into lines, and as a sequence of lines grouped into pages. The specification of the package is given below in subc ...point of view, a text file is a sequence of pages, a page is a sequence of lines, and a line is a sequence of characters; the end of a line is marked by a '
    6 KB (1,068 words) - 16:49, 1 May 2019
  • The text of a compilation is divided into <span id="I1170"></span>''lines''. <span id="I1171"></span>In general, the representation for an end of lin An implementation shall support lines of at least 200 characters in length, not counting any characters used to s
    4 KB (507 words) - 23:36, 4 May 2019
  • ...mation for debugging. For example, they allow you to view specified source lines, program execution statistics, the call chain, current tasks, and so forth. ...d range of source [[PowerAda:APPENDIX A. Glossary#MARKER-9-1024|''code'']] lines from a given [[PowerAda:APPENDIX A. Glossary#MARKER-9-1026|''compilation un
    13 KB (1,852 words) - 00:36, 25 April 2019
  • History entries can be used to construct new command lines, using the history reference indicator. For example, if history entry 10 is ...he first line of a macro definition the debugger prompts you to enter more lines until the definition is finished. No syntax check is made to any line that
    12 KB (1,849 words) - 00:35, 25 April 2019
  • 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
  • ...the View Tag, to the VOB Path name. For example, the two following command lines will produce the same output for a view named delta_view within a VOB tagge
    1 KB (222 words) - 01:36, 24 April 2019
  • ...braries. The sublibraries are listed one per line, interspersed with blank lines or comments. Every required sublibrary must be listed in the library list f
    2 KB (265 words) - 21:53, 14 April 2019
  • ...the new adalib.imports file (note that you do not need to include comment lines beginning -- so in fact the specs adalib.imports file can be completely bla -- lines in this file may be:
    14 KB (2,482 words) - 00:37, 25 April 2019
  • ...div><div class="linenumbers">{{DISPLAYTITLE: A.10.5 Operations on Columns, Lines, and Pages}} ...same way as a Get procedure (see [[Guide:95lrm/RM-A-10-6|A.10.6]]). (Short lines will be skipped until a line is reached that has a character at the specifi
    10 KB (1,678 words) - 17:19, 1 May 2019
  • ...Debugger: adbg/Unit Browser#MARKER-9-718|''Outline Pane'']] will show all lines in which an occurrence of the searched-for string or construct is found.
    2 KB (263 words) - 15:30, 23 April 2019
  • :Precede each NUM lines with its line number. ;-L, --lines-per-page=NUM
    8 KB (1,162 words) - 00:36, 25 April 2019
  • ...or CHARACTERS. If not specified, the default value is LINES. If the value LINES is selected, the input terminal is processed in canonical mode. If the valu ...nonical mode input processing, the terminal input is processed in units of lines. A line is delimited by a newline character, an end-of-file character, or a
    11 KB (1,797 words) - 00:36, 25 April 2019
  • ...r the application runs, the closer RootCause gets to pinpointing the exact lines of problem code. The result is source-level information about where a probl
    2 KB (241 words) - 03:27, 21 December 2018
  • ...xed price. A typical engagement for an embedded application with a million lines of code would be about $150,000.
    2 KB (282 words) - 03:31, 21 December 2018
  • ...xed price. A typical engagement for an embedded application with a million lines of code would be about $150,000.
    2 KB (282 words) - 03:31, 21 December 2018
  • ...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
  • ...irs of lines, with the project-relative pathname of a file on odd-numbered lines, and the information associated with the file on the following even-numbere
    5 KB (890 words) - 00:35, 25 April 2019
  • Is there a simple probe that just traces the lines in one routine? (trace.ual seems a bit of overkill)
    2 KB (352 words) - 03:20, 21 December 2018
  • ...r the application runs, the closer RootCause gets to pinpointing the exact lines of problem code. The result is source-level information about where a probl
    2 KB (300 words) - 03:27, 21 December 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.
    49 KB (6,266 words) - 18:19, 7 December 2022
  • ...is 52 lines long, followed by the body of package EXAMPLE_TWO, which is 40 lines long. The numbers to the right of the sample, and the dashes preceding them ...n with line numbers, you would obtain the numbers to use to specify source lines. The SOURCE command performs part of this function by displaying sections o
    18 KB (2,585 words) - 00:35, 25 April 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
  • ...r the application runs, the closer RootCause gets to pinpointing the exact lines of problem code. The data you collect with RootCause allows you to provide
    2 KB (327 words) - 03:27, 21 December 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
  • ...ing standards, modify the configuration as described above by adding these lines: ...LRM95 capitalization. If this is not appropriate, add one of the following lines to your configuration file:
    7 KB (1,095 words) - 00:35, 25 April 2019
  • ...#MARKER-9-1750|adbg]]''. It provides a point-and- click interface in which lines and objects are designated by selection in the Ada source text, and operati
    4 KB (575 words) - 00:35, 25 April 2019
  • 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
  • ...''debugger'']] variables facility allows you to construct debugger command lines using variable names to replace frequently used strings. There are several splitting a command over two lines"</syntaxhighlight>
    14 KB (2,073 words) - 00:37, 25 April 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
  • (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
  • ...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 "==&gt;" parts of the traceback are necessary at the beginnin
    18 KB (2,825 words) - 18:30, 6 November 2023
  • (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
  • (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
  • ...ion for Debugging#MARKER-9-1966|SOURCE]] command to determine which source lines can have ''breakpoint''s set on them. To set a breakpoint at the entry or e ...for a description of how the debugger indicates on a source display those lines where you can set ''breakpoint''s. The following guidelines specify the loc
    27 KB (4,121 words) - 00:37, 25 April 2019
  • ...e pane is a small list above the source in the browser window. It displays lines from the source. Clicking on a line in the outline pane moves the cursor to
    5 KB (828 words) - 16:37, 23 April 2019
  • (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
  • (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
  • ...ify any file names on the command line. The list of file names can contain lines with "--" in them; the source formatter ignores the remainder of the line a
    5 KB (744 words) - 00:35, 25 April 2019
  • 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
  • ...e the [[#MARKER-9-722|''Source Pane'']] in the browser window. It displays lines from the corresponding source pane. Clicking on a line in the outline pane ...l'' instead, the contents [[#MARKER-9-718|''Outline Pane'']] will show all lines in which an occurrence of the searched-for string or construct is found.<sp
    13 KB (2,192 words) - 00:36, 25 April 2019

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