Search results

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

Page title matches

Events Predefined Probe
== Performance Probe: events.ual == ...obe records the start and end times of program functions and user-defined "events", organizes them by call tree, and provides several reports which help to a

18 KB (2,740 words) - 19:07, 7 October 2022

Page text matches

PowerAda:APPENDIX C. Implementation Characteristics/Annex M/109
...s/Annex M/109|Displaytitle=|Chapter=C|Section=109|Order=96.117|Summary=Any events that can result in a partition becoming inaccessible. See E.1(7).|Product=P == (109) Any events that can result in a partition becoming inaccessible. ==

505 bytes (67 words) - 00:31, 24 April 2019
PowerAda:APPENDIX C. Implementation Characteristics/Annex M/111
...stics/Annex M/111|Displaytitle=|Chapter=C|Section=111|Order=96.119|Summary=Events that cause the version of a compilation unit to change. See E.3(5).|Product == (111) Events that cause the version of a compilation unit to change. ==

501 bytes (69 words) - 00:31, 24 April 2019
Events Predefined Probe
== Performance Probe: events.ual == ...obe records the start and end times of program functions and user-defined "events", organizes them by call tree, and provides several reports which help to a

18 KB (2,740 words) - 19:07, 7 October 2022
RCUG 0 Contents
: [[RCUG_RootCause_GUI_Reference#HEADING11-538|Select Events Dialog]] : [[RCUG_RootCause_GUI_Reference#HEADING11-554|Find Text In Events Dialog]]

9 KB (1,118 words) - 21:35, 4 March 2018
RCUG 5 RootCause Demo
...ARKER-9-1725|Trace Display]] window, the window for viewing all trace events. On the left is the Event Tree; on the upper right is the source/text windo 

29 KB (4,850 words) - 17:20, 19 June 2018
RCUG Index
[[RCUG_RootCause_GUI_Reference#events|events]] ...otCause_GUI_Reference#Find Function In Trace Events|Find Function In Trace Events]]

41 KB (5,233 words) - 22:40, 22 March 2019
Guide:95lrm/RM-E-3
...g of "semantically significant". It is unspecified whether there are other events (such as recompilation) that result in the version of a compilation unit ch

2 KB (398 words) - 23:15, 1 May 2019
AUG Index
[[Events_Predefined_Probe#Events_UAL_Configuration_Probe|Events Probe]] [[Events_Predefined_Probe|events]]

34 KB (4,340 words) - 23:07, 27 February 2019
AUG Predefined Probes
...of this appendix, we'll refer to these by their simple filename: coverage, events, profile, trace, memwatch, etc. ...the trace probe in overhead. In fact trace may be used in conjunction with events in order to provide load-shedding, even if nothing was traced.

17 KB (2,770 words) - 23:06, 27 February 2019
Guide:95lrm/RM-D-2-2
Each of the events specified above is a task dispatching point (see [[Guide:95lrm/RM-D-2-1|D.2

5 KB (770 words) - 22:49, 1 May 2019
Guide:95lrm/RM-E-1
...it becomes inaccessible to other partitions. Other implementation-defined events can also result in a partition becoming inaccessible.

5 KB (720 words) - 15:48, 29 April 2019
RCUG RootCause Files and Environment Variables
...use log file may also contain other messages and debug information as TEXT events. The RootCause log file may be examined in the GUI and used as a starting p

28 KB (4,452 words) - 03:18, 26 June 2018
RCUG RootCause GUI Reference
...Ada) exceptions that occur in the program. These will show up as exception events in the [[#MARKER-9-1680|Trace Index Dialog]], and a full [[RCUG_3_ ...be displayed when you define a trace, and also when you view logged trace events. This will open the [[#MARKER-9-1504|Edit Source Path Dialog]].

120 KB (21,077 words) - 19:32, 22 March 2019
RCUG 3 Terminology and Concepts
[[#MARKER-9-407|Data File]]s;<LI>special events in the individual events in the

43 KB (6,767 words) - 22:29, 17 July 2018
Guide:95lrm/RM-A-10-5
...e input or output of sufficiently many characters, lines, or pages). These events do not cause any exception to be propagated. However, a call of Col, Line,

10 KB (1,678 words) - 17:19, 1 May 2019
Guide:95lrm/RM-C-3
An ''interrupt'' represents a class of events that are detected by the hardware or the system software. 

7 KB (1,130 words) - 15:48, 29 April 2019
Memwatch Predefined Probe
The heap allocation and deallocation events can be examined in more detail, later, by formatting the recorded data to p ...he number of unique tracebacks found among the allocation and deallocation events. This will reduce the memory available to your application program. So, if

18 KB (2,825 words) - 18:30, 6 November 2023
Trace Predefined Probe
...emory and writes it out to an APD file. Taking periodic snapshots at known events, like the entry or exit to a particular subprogram, allows you to compare a ...rcular memory buffer instead, and write out its contents only at specified events to an APD file.

22 KB (3,480 words) - 23:37, 20 March 2018
PowerAda:APPENDIX C. Implementation Characteristics/Annex M
...a:APPENDIX C. Implementation Characteristics/Annex M/109|'''(109)''' - Any events that can result in a partition becoming inaccessible. See E.1(7).]] ...erAda:APPENDIX C. Implementation Characteristics/Annex M/111|'''(111)''' - Events that cause the version of a compilation unit to change. See E.3(5).]]

24 KB (3,169 words) - 02:53, 24 April 2019
RCUG 4 Getting Started
..._GUI_Reference#Find|Find]] button to search for specific functions or events in the data.

11 KB (1,781 words) - 23:20, 17 July 2018