Search results

Jump to: navigation, search

Page title matches

  • == 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

  • ...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
  • ...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
  • == 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_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
  • ...ARKER-9-1725|Trace Display]]</EM> window, the window for viewing all trace events. On the left is the Event Tree; on the upper right is the source/text windo <!-- [["rcc-11.html#MARKER-9-1699">Select Events</DIV> -->
    29 KB (4,850 words) - 17:20, 19 June 2018
  • [[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
  • ...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
  • [[Events_Predefined_Probe#Events_UAL_Configuration_Probe|Events Probe]] [[Events_Predefined_Probe|events]]
    34 KB (4,340 words) - 23:07, 27 February 2019
  • ...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
  • <span id="I6552"></span><span id="I6553"></span>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
  • ...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
  • ...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
  • ...Ada) exceptions that occur in the program. These will show up as exception events in the <EM>[[#MARKER-9-1680|Trace Index Dialog]]</EM>, and a full [[RCUG_3_ ...be displayed when you define a trace, and also when you view logged trace events. This will open the <EM>[[#MARKER-9-1504|Edit Source Path Dialog]]</EM>.
    120 KB (21,077 words) - 19:32, 22 March 2019
  • [[#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
  • ...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
  • <span id="I6373"></span>An ''interrupt'' represents a class of events that are detected by the hardware or the system software. <span id="I6374">
    7 KB (1,130 words) - 15:48, 29 April 2019
  • 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
  • ...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
  • ...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
  • ..._GUI_Reference#Find|Find]]</em> button to search for specific functions or events in the data.
    11 KB (1,781 words) - 23:20, 17 July 2018
  • ==== 4.5 Can I cause only APP_TRACED events to show up in the RootCause Log? ==== ==== 7.1 Why are some functions found in the traced Events not found in the Trace Setup? ====
    73 KB (12,088 words) - 21:47, 9 May 2017
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    44 KB (6,135 words) - 13:58, 20 December 2018
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    45 KB (6,325 words) - 21:21, 25 October 2019
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    46 KB (6,407 words) - 01:34, 6 March 2020
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    46 KB (6,444 words) - 01:58, 2 February 2021
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    47 KB (6,597 words) - 18:56, 13 September 2021
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    48 KB (6,635 words) - 17:14, 22 September 2021
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    48 KB (6,656 words) - 16:55, 4 October 2021
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    48 KB (6,681 words) - 16:52, 16 February 2022
  • 5. 'Find Function in Trace Events' now works from Event Summary Tree. (i902) 21. Re-enabled support for DisplayReport SubtotalReport in events.apc. (i1310)
    48 KB (6,698 words) - 17:26, 8 September 2022
  • * Any events that can result in a partition becoming inaccessible. See E.1(7).
    13 KB (1,817 words) - 10:20, 2 May 2019
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    60 KB (8,488 words) - 13:59, 20 December 2018
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    61 KB (8,594 words) - 21:23, 25 October 2019
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    61 KB (8,649 words) - 01:35, 6 March 2020
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    62 KB (8,700 words) - 19:22, 1 February 2021
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    62 KB (8,772 words) - 17:47, 13 September 2021
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    62 KB (8,792 words) - 17:02, 22 September 2021
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    62 KB (8,800 words) - 16:57, 4 October 2021
  • 32. (1310) re-enable 'DisplayReport SubtotalReport' in events.ual 8. The operation "Find Function in Trace Events" now works for Summary nodes
    63 KB (8,818 words) - 16:54, 16 February 2022
  • ...or after examining variables. Execution then continues until one of these events takes place:
    27 KB (4,121 words) - 00:37, 25 April 2019
  • ...ots|Configuration of Snapshots]]). Taking such periodic snapshots at known events, like the entry to or exit from a particular function, may help correlate s
    36 KB (4,378 words) - 06:24, 20 March 2018
  • ...es for choosing among the tasks waiting in entry queues.) This sequence of events will be repeated until the entry queue for Wait is empty. When the Wait que ...olated information- hiding principles, and caused race conditions, because events could occur between the multiple calls.
    100 KB (15,667 words) - 16:19, 20 April 2019
  • ...ay be preempted, but otherwise it runs to completion without blocking. The events that can trigger the invocation of task groups include interrupts and actio ...tion to wait for an event, and to abort blocking operations in response to events. This would have allowed the application to provide its own timer services.
    150 KB (24,418 words) - 16:20, 20 April 2019
  • ...ots|Configuration of Snapshots]]). Taking such periodic snapshots at known events, like the entry to or exit from a particular function, may help correlate s
    49 KB (6,266 words) - 18:19, 7 December 2022
  • ==== 15.12 How do I use this "events" probe everyone's talking about? ==== ...e 2.0.5 (Aprobe 4.2.5) there's an example under examples/predefined_probes/events, and documentation in Appendix D of the Aprobe User's Guide. Here's a quick
    162 KB (25,627 words) - 17:12, 20 September 2021
  • ...specify that a task is willing to wait for any of a number of alternative events. Select statements take various forms.
    67 KB (10,189 words) - 16:20, 20 April 2019
  • In order to associate logged data with events in a program's execution, facilities to log the time and thread context of
    102 KB (15,018 words) - 23:05, 27 February 2019
  • ...to be used in different circumstances according to the arrival pattern of events; see [Sha 90a] and [Klein 93].
    101 KB (16,126 words) - 20:41, 23 April 2019