Search results

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

OCS:Memory Links
...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
OCS:Sensorpoint SureStart
...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
OCS:Sensorpoint SureStart Service
...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
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
PowerAda:Project Management with PowerAda/Customizing the Configuration Management Integration
...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
OCS:Probe Library
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
OCS:Performance Bottlenecks
...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
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
PowerAda:APPENDIX F. Debugger Command Reference
...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
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
OCS:Integration
...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
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
PowerAda:Project Management with PowerAda/Site-Specific Customization
...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
PowerAda:The PowerAda Debugger: adbg
...#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
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
PowerAda:APPENDIX F. Debugger Command Reference/Manipulating Debugger and Program Variables
...''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
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