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
  • 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
  • You can select the number of lines for the window as<br />
    6 KB (881 words) - 21:53, 14 April 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
  • ...le is meant to apply when ''EF''.Float_Type'Signed_Zeros is False; the two lines just above it, when ''EF''.Float_Type'Signed_Zeros is True and the paramete
    6 KB (900 words) - 09:04, 2 May 2019
  • ..._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
  • :Outputs the value of the parameter Item as an integer literal, with no low lines, no exponent, and no leading zeros (but a single zero for the value zero),
    6 KB (913 words) - 17:27, 1 May 2019
  • 28  A string read by Get or written by Put can extend over several lines. An implementation is allowed to assume that certain external files do not
    7 KB (1,080 words) - 17:24, 1 May 2019
  • ...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
  • (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
  • ...int of instantiation in the compilation unit. Subsequent integers refer to lines within instantiated generics. The ''Integer'' <code>s</code> refers to the ...PPENDIX A. Glossary#MARKER-9-1032|''debugger'']]. However, if you know the lines in the generic where you can set [[PowerAda:APPENDIX A. Glossary#MARKER-9-1
    15 KB (2,346 words) - 00:36, 25 April 2019
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    22 KB (3,033 words) - 21:22, 25 October 2019
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    23 KB (3,108 words) - 01:35, 6 March 2020
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    23 KB (3,151 words) - 19:21, 1 February 2021
  • ...and line (or on standard input if <code>-I</code> is used). The Ada source lines are preceded by line numbers to make it easier to locate specific places wi ...nts of the corresponding Ada file, together with information to map source lines to assembler statements, and so may not be in a correct format for the AIX
    27 KB (4,407 words) - 00:36, 25 April 2019
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    24 KB (3,264 words) - 17:46, 13 September 2021
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,323 words) - 16:56, 4 October 2021
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,348 words) - 16:53, 16 February 2022
  • (2586) Linux64 quietly ignores lines not instrumented (2492) axdln doesn't tolerate # lines
    25 KB (3,365 words) - 17:25, 8 September 2022
  • :Initiates a dialog to execute source lines, stepping into calls. See [[PowerAda:APPENDIX F. Debugger Command Reference :Initiates a dialog to execute source lines, skipping over calls. See [[PowerAda:APPENDIX F. Debugger Command Reference
    22 KB (3,387 words) - 00:36, 25 April 2019
  • Highlight all of the procedure Put and choose ''Indent Lines In Region'' from the ''Ada'' menu and watch what happens. Ada-mode will aut
    8 KB (1,317 words) - 00:37, 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 ...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
  • * 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
  • (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
  • 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
  • (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
  • (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
  • (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
  • In addition, progress lines are written to stderr, like
    10 KB (1,565 words) - 18:31, 6 November 2023
  • ...KER-9-629"></span>POWERADA_BASELINES file. This is simply a text file with lines of the form:
    13 KB (2,064 words) - 00:36, 25 April 2019
  • (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
  • (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
  • (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
  • (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
  • (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
  • ...dow has split into two views. The top view is a "brief" listing of all the lines where <code>Track</code> is referenced; in a large file, you can click the
    13 KB (2,115 words) - 00:34, 25 April 2019
  • (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
  • // 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
  • ...<code>adalib.imports</code> file should be empty (or contain only comment lines). If another sublibrary contains a unit needed by a unit in this sublibrary
    16 KB (2,590 words) - 00:35, 25 April 2019
  • (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
  • (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
  • 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
  • (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
  • type Terminal_Input_Values is (Lines, Characters); Terminal_Input : Terminal_Input_Values := Lines;
    59 KB (6,892 words) - 02:45, 24 April 2019
  • (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
  • (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
  • (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
  • 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
  • (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
  • 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
  • 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
  • 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
  • | Displays the source lines containing the declaration of the type of Object specified.
    17 KB (2,527 words) - 00:36, 25 April 2019
  • <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
  • 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
  • ...ifier causes the debugger to insert or omit, the display of the Ada source lines intermixed with the disassembly display. The default is NOSOURCE.
    20 KB (2,947 words) - 14:02, 24 April 2019
  • ...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
  • ...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
  • : 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
  • ...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
  • A.10.5 [[Guide:95lrm/RM-A-10-5|Operations on Columns, Lines, and Pages]]
    19 KB (2,641 words) - 15:48, 29 April 2019
  • - all other lines that follow are assumed to apply to this module, up until the next ''module
    23 KB (3,864 words) - 20:43, 12 May 2021
  • [[AUG_Aprobe_API_Reference#Line Iterator|for lines]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • ...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
  • (b) references to specific source lines; where mygrep.args might contain the lines:
    162 KB (25,627 words) - 17:12, 20 September 2021
  • :A.10.5 [[Guide:95lrm/RM-A-10-5|Operations on Columns, Lines, and Pages]]
    21 KB (2,643 words) - 05:19, 6 May 2019
  • The lines in the above example indicate the separate compilation units; they may be s
    67 KB (10,189 words) - 16:20, 20 April 2019