blob: dfb0a850b48d908ea249ddebb3c2ab5ef3d3f083 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
//$Id$
Case
----
This is a test for forking new DTs from existing DTs using
Current::spawn (). A local DT is created with
Current::begin_scheduling_segment() and
Current::end_scheduling_segment (). A new DT is spawned within the
context of the DT created. The Thread_Action::do () method is called
when the spawned DT is activated. This method provides a point of
entry for the spawned DT.
This test also shows that the DT spawn should be made only within the
context of another DT.
To Run
-------
./test
Typical Output
--------------
Invoking DT spawn without calling begin_scheduling_segment...
(7141|1024) EXCEPTION, Spawn should be in the context of a Scheduling Segment
system exception, ID 'IDL:omg.org/CORBA/BAD_INV_ORDER:1.0'
TAO exception, minor code = 0 (unknown location; unspecified errno), completed = NO
Start - Scheduling Segment...
The Current DT Guid is 1
Spawning a new DT...
End - Scheduling Segment 1
Test_Thread_Action::do Harry Potter
The spawned DT Guid is 2
Segment Names for DT 2:
Chamber of Secrets
|