Fixed fuzz

18 files changed, 84 insertions, 69 deletions

diff --git a/TAO/tests/Alt_Mapping/README b/TAO/tests/Alt_Mapping/README
index a1aae3b61a1..b34fd7c769c 100644
--- a/TAO/tests/Alt_Mapping/README
+++ b/TAO/tests/Alt_Mapping/README
@@ -30,7 +30,7 @@ To run the server, type
           arguments to ORB_init start with the letters -ORB. Please
           see TAO documentattion on all the supported arguments
 
-          -d for debugging. 
+          -d for debugging.
 	  -o <ior_output_file> for outputting the servant IOR to a file.
 
 To run the client, type
@@ -42,7 +42,7 @@ To run the client, type
    [-d]                                 debugging
    [-n loopcount]                       number of times to run the test
    [-f servant-IOR-file]		            reads the servant-IOR from the
-                                        specified file. 
+                                        specified file.
    [-k Param_Test-obj-ref-key]          object key of Param_Test object
    [-i invocation (sii/dii)]            default is static invocation
                                         interface. To use DII, type
@@ -58,7 +58,7 @@ To run the client, type
 
 	1. Using the -f option to read the IOR from a file.
 
-	2. Using the -k option to read the IOR from the 	
+	2. Using the -k option to read the IOR from the
 	   command line.
 
 run_test.pl:
@@ -66,8 +66,8 @@ run_test.pl:
 	There is a perl script in this directory named run_test.pl to
         test all the types. It starts the server first and then runs
         the client with the different data type parameters. The
-        arguments it takes are: 
-	
+        arguments it takes are:
+
 	      -n num              -- runs the client num times (default is 5)
         -d                  -- runs each in debug mode
         -onewin             -- keeps all tests in one window on NT
diff --git a/TAO/tests/BiDirectional_MultipleORB/README b/TAO/tests/BiDirectional_MultipleORB/README
index 2d26bcc817e..aaeca1ead16 100644
--- a/TAO/tests/BiDirectional_MultipleORB/README
+++ b/TAO/tests/BiDirectional_MultipleORB/README
@@ -1,16 +1,16 @@
-# $Id$
+$Id$
 
 This is a test that creates a birectional GIOP policy for a POA and then
 attempts to repeat this, after destructing and re-creating the ORB. This used to
-fail by breaking an assertion, because the second ORB was tryig to register a policy 
-validator object instance, which lingered since the time the first ORB was created. 
+fail by breaking an assertion, because the second ORB was tryig to register a policy
+validator object instance, which lingered since the time the first ORB was created.
 
 The validators are chained in a linked list, and any attempt to register a new one,
 which already points to another, is considered an error:
 
 ACE_ASSERT: (24189|4143901376) file Policy_Validator.cpp, line 28 assertion failed for 'validator->next_ == 0'.Aborting...
 
-In other instances it broke with SEGV, when trying to access an previously deleted 
+In other instances it broke with SEGV, when trying to access an previously deleted
 bi-dir policy validator.
 
 For additional detail reffer to RT4667 and RT4672.
diff --git a/TAO/tests/Bug_2144_Regression/README b/TAO/tests/Bug_2144_Regression/README
index 78e177a24c7..a893cd6aa5d 100644
--- a/TAO/tests/Bug_2144_Regression/README
+++ b/TAO/tests/Bug_2144_Regression/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
 
 There is nothing to run for this test. It passes if the generated code
-compiles. See bugzilla #2144. 
+compiles. See bugzilla #2144.
diff --git a/TAO/tests/Bug_3845_Regression/README b/TAO/tests/Bug_3845_Regression/README
index 281aa032421..d3e6ea8267b 100644
--- a/TAO/tests/Bug_3845_Regression/README
+++ b/TAO/tests/Bug_3845_Regression/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page Local/Remote Mismatch Test README File
 
 	This test does not use the C++ compiler or any binaries
@@ -8,14 +10,14 @@
 	successfully if it catches the expected error. If the
 	expected error is not returned by the IDL compiler,
 	the script itself returns an error.
-	
+
 	In each of the 4 IDL files:
-	
+
 	local_inarg.idl
 	local_inoutarg.idl
 	local_outarg.idl
 	local_rettype.idl
-	
+
 	there is an IDL error in which a local interface is used as
 	the indicated part of the signature of an operation on a
 	non-local interface. If the error were not caught in the
diff --git a/TAO/tests/CDR/README b/TAO/tests/CDR/README
index 0a6c4192d6e..83c3242abe9 100644
--- a/TAO/tests/CDR/README
+++ b/TAO/tests/CDR/README
@@ -1,4 +1,4 @@
-# $Id$
+$Id$
 
 This directory contains the following tests for the CDR stream class;
 
@@ -6,15 +6,15 @@ This directory contains the following tests for the CDR stream class;
 
           Simply encodes a lot of CORBA::Octets, CORBA::Short and
           CORBA::Long into a CDR stream and then decodes them;
-          verifying that the same results are obtained. 
+          verifying that the same results are obtained.
 
         . growth
-        
+
           Helps measure how the growth strategy affects the
           performance of CDR streams.
 
         . tc
-        
+
           TAO implements TypeCodes using a CDR buffer (this was
           inherited from the Sun IIOP engine), this test verifies that
           some of the basic TypeCodes actually are able to interpret
diff --git a/TAO/tests/DII_AMI_Forward/README b/TAO/tests/DII_AMI_Forward/README
index 2c493a3c740..360d01250ab 100644
--- a/TAO/tests/DII_AMI_Forward/README
+++ b/TAO/tests/DII_AMI_Forward/README
@@ -1,22 +1,23 @@
 /**
+
 $Id$
 
 @page DII_AMI_Forward Test README File
 
 This test illustrates the new feature outlined in bug 3105 for
-supporting the detection and handling of a LOCATION FORWARD 
+supporting the detection and handling of a LOCATION FORWARD
 exception within a DII based asynch invocation.
 
 DII Asynch reply handlers operate very close to the TAO internals,
 receiving raw CDR buffers as parameters rather than collections of
 arguments. This example is built on apriori knowledge of the nature
-of the call and its return type in order to work. A more general 
-purpose handler would take a reference to the request instance in 
+of the call and its return type in order to work. A more general
+purpose handler would take a reference to the request instance in
 order to handle a variety of responses. As such, it is impractical
 to have a single instance of the reply handler supporting more than
 one pending invocation.
 
-This test is designed around a server that, on the receipt of the 
+This test is designed around a server that, on the receipt of the
 first invocation raises a location forward exception. The client's
 DII asynch reply handler then reissues the invocation using the new
 object reference and finally handles the reply.
diff --git a/TAO/tests/DII_Collocation_Tests/twoway/README b/TAO/tests/DII_Collocation_Tests/twoway/README
index 77df8565097..b73deb93730 100644
--- a/TAO/tests/DII_Collocation_Tests/twoway/README
+++ b/TAO/tests/DII_Collocation_Tests/twoway/README
@@ -1,23 +1,23 @@
-# $Id$
+$Id$
 
-NOTE: This test has not completed yet !!!. This test currently just tested with "IN" 
-arguments. The OUT, INOUT and RETURN arguments test cases need be added. 
+NOTE: This test has not completed yet !!!. This test currently just tested with "IN"
+arguments. The OUT, INOUT and RETURN arguments test cases need be added.
 
 
 Description:
-This test is used to test the bug fix on collocated dii twoway request 
-invocation via invoke() crash on get_in_arg() when the request has multiple 
+This test is used to test the bug fix on collocated dii twoway request
+invocation via invoke() crash on get_in_arg() when the request has multiple
 "IN" parameters.
 
 The test.idl defines twoway operations with all sorts "IN" SArgument to test the
-conversion of the DII parameters in NVList to the list of arguments. 
+conversion of the DII parameters in NVList to the list of arguments.
 It also defines the operations with multiple "IN" arguments to test the
 bug fix.
 
 
-This test is a modification of the DII_Collocation_Tests/oneway test. The 
+This test is a modification of the DII_Collocation_Tests/oneway test. The
 idl interfaces define twoway method instead of oneway and the client invokes
-the twoway operations via invoke() instead of oneway operations via 
+the twoway operations via invoke() instead of oneway operations via
 send_oneway().
 
 
diff --git a/TAO/tests/DSI_AMI_Gateway/README b/TAO/tests/DSI_AMI_Gateway/README
index 93f3c77df24..89fa9f9b0a5 100644
--- a/TAO/tests/DSI_AMI_Gateway/README
+++ b/TAO/tests/DSI_AMI_Gateway/README
@@ -1 +1,3 @@
-a simple test to experience the whole AMI+DII+AMH+DSI feature. 
+$Id$
+
+a simple test to experience the whole AMI+DII+AMH+DSI feature.
diff --git a/TAO/tests/MProfile_Connection_Timeout/README b/TAO/tests/MProfile_Connection_Timeout/README
index 85dc6e4d7ed..99202b0912a 100644
--- a/TAO/tests/MProfile_Connection_Timeout/README
+++ b/TAO/tests/MProfile_Connection_Timeout/README
@@ -1,5 +1,7 @@
 /**
 
+$Id$
+
 @page MProfile_Connection_Tiemout Test README File
 
 	The simplest possible test for connection timeouts across
@@ -9,11 +11,11 @@ timeout policy is set. If connection_timeout policy is set and if the
 client is not anle to establish connection using one of the profiles,
 the client should fail over to the next profile seamlessly. The test
 has been constructed to check for this feature.
-         
+
         Please refrain from "improving", extending or expanding this
-test. 
+test.
 
-@todo: We need to write a MT test for this feature. 
+@todo: We need to write a MT test for this feature.
 
 	To run the test use the run_test.pl script:
 
diff --git a/TAO/tests/MProfile_Forwarding/README b/TAO/tests/MProfile_Forwarding/README
index 518d6d7ec14..9a8dee07935 100644
--- a/TAO/tests/MProfile_Forwarding/README
+++ b/TAO/tests/MProfile_Forwarding/README
@@ -1,10 +1,12 @@
+$Id$
+
 This test evalutes ORB fault tolerance support, based on one of the
 problems that was reported by the DOORS team at Lucent. The test is
 aimed at testing the following scenario.
 
 1. We will have three copies of the same server running. Let me call
    them as ref1, ref2 & ref3.
-     
+
 2. We will have a manager application which does the following. Hosts
    a POA with the policies set for a Servant_Locator.  Then it creates
    the reference on that and does the following
@@ -17,7 +19,7 @@ aimed at testing the following scenario.
 
 3. The client starts by reading  the IOR written to a file by the
    Manager,  that was created by 2a.  The client basically makes a remote
-   call and a shutdown call on the remote objects in a loop ie. multiple times. 
+   call and a shutdown call on the remote objects in a loop ie. multiple times.
 
    a. When the first call is made, the call is responded by the server who published
       ref1. He is then shutdown.
@@ -25,9 +27,9 @@ aimed at testing the following scenario.
       is also shutdown next.
    c. On the third call, the call first comes to the preinvoke () method in the
       Locator class who throws the ForwardRequest exception with the IOR created in
-      2b.  
+      2b.
    d. After the exception is thrown the calls get resolved on the server
-     who published ref3. He is also shutdown next. 
+     who published ref3. He is also shutdown next.
 
 The above sequence SHOULD be seen to consider the test as being
 succesfull.
@@ -37,20 +39,20 @@ To run the test
 
 * Start three copies of the server like this
 
-  $ ./server -o file1.ior 
-  $ ./server -o file2.ior 
-  $ ./server -o file3.ior 
+  $ ./server -o file1.ior
+  $ ./server -o file2.ior
+  $ ./server -o file3.ior
 
 * Then start the Manager like this
 
   $ ./Manager -a file://file1.ior -b file://file2.ior -c \
-    file://file3.ior -d file4.ior 
+    file://file3.ior -d file4.ior
 
    (The above should be on the same line in the command prompt. The
    file4.ior is for publishing the first merged IOR (refer step 2.a).
 
 * The start the client like this
-  
+
   $ ./client -o file://file4.ior
 
 
diff --git a/TAO/tests/NestedUpcall/MT_Client_Test/README b/TAO/tests/NestedUpcall/MT_Client_Test/README
index e1827ccb167..823d15c3018 100644
--- a/TAO/tests/NestedUpcall/MT_Client_Test/README
+++ b/TAO/tests/NestedUpcall/MT_Client_Test/README
@@ -1,10 +1,11 @@
+$Id$
 
 Multiple Client and global resources test
 =========================================
 
 
 This test uses global resources, meaning one ORB and one Reactor.
-Several client threads are created, which call one of the two servers. 
+Several client threads are created, which call one of the two servers.
 This means, two server instances should be running. Also one
 server thread is running, doing nested upcalls to the same server.
 
@@ -12,7 +13,7 @@ The intention is to see if global resources with multiple threads work.
 
 The client understands the following switches:
 
--f file of the ior of the first server, used by approx. half of the 
+-f file of the ior of the first server, used by approx. half of the
    client threads and the local server thread.
 
 -g file of the ior of the second server
diff --git a/TAO/tests/NestedUpcall/Triangle_Test/README b/TAO/tests/NestedUpcall/Triangle_Test/README
index d946e466421..b6a37c5c9b9 100644
--- a/TAO/tests/NestedUpcall/Triangle_Test/README
+++ b/TAO/tests/NestedUpcall/Triangle_Test/README
@@ -1,23 +1,24 @@
 $Id$
+
 Documentation about the Triangle test
 
 Purpose:
 
 Is to show how nested upcalls are handled.
 
-Three objects exist: 
+Three objects exist:
 Object A, Object B and the Initiator
 
 The initiator calls a two-way call foo on object A,
 object A calls foo_object_B, a one-way call, on the initiator,
 this causes initiator to call foo on object B,
 this causes object B to (oneway) call finish on object A,
-this causes object A to return from its first two-way call 
+this causes object A to return from its first two-way call
 (before object B returns from its two-way call),
 after a second or so object B returns from its two-way call.
 
-The printed order should show, that the replies are 
-handled in the stack order, but not in the actual 
+The printed order should show, that the replies are
+handled in the stack order, but not in the actual
 arriving order.
 
 To start:
diff --git a/TAO/tests/No_Server_MT_Connect_Test/README b/TAO/tests/No_Server_MT_Connect_Test/README
index 95bcacddc97..4c66e87994f 100644
--- a/TAO/tests/No_Server_MT_Connect_Test/README
+++ b/TAO/tests/No_Server_MT_Connect_Test/README
@@ -1,18 +1,20 @@
 /**
 
+$Id$
+
 @page No_Server_MT_Connect_Test  README File
 
       The objective of the test is to track the behavior of the
 multi-threaded client when no server is present to connect. The client
 uses all the connect strategies provided by the ORB. All the client
-threads should exit gracefully. 
+threads should exit gracefully.
 
 This test is to make sure (hopefully) the refcount mechanism on the
 handler used that safeguards handlers getting deleted when the
-connection establishment fails. 
+connection establishment fails.
 
 	Please refrain from "improving", extending or expanding this
-test, if you need to change 
+test, if you need to change
 
 	To run the test use the run_test.pl script:
 
diff --git a/TAO/tests/RTCORBA/Private_Connection/README b/TAO/tests/RTCORBA/Private_Connection/README
index 8ba353b0f57..1e4041f64e7 100644
--- a/TAO/tests/RTCORBA/Private_Connection/README
+++ b/TAO/tests/RTCORBA/Private_Connection/README
@@ -2,8 +2,8 @@ $Id$
 
 This is a unit test for RTCORBA::PrivateConnectionPolicy.
 
-Description.  
--------- 
+Description.
+--------
 The server creates two servants, registers them with the Root POA,
 prints out their IORs and waits for the requests from the client.  The
 client obtains the IORs, makes several invocations on the objects,
diff --git a/TAO/tests/RTCORBA/Profile_And_Endpoint_Selection/README b/TAO/tests/RTCORBA/Profile_And_Endpoint_Selection/README
index ba49c18a341..dc2992f1d9a 100644
--- a/TAO/tests/RTCORBA/Profile_And_Endpoint_Selection/README
+++ b/TAO/tests/RTCORBA/Profile_And_Endpoint_Selection/README
@@ -8,28 +8,28 @@ below.
 
 Client: The client does the following:
 
-- vanilla invocations 
+- vanilla invocations
 - sets private connection
-- vanilla invocations 
+- vanilla invocations
 - reset
 
 - sets client protocols
-- vanilla invocations 
+- vanilla invocations
 - sets private connection
-- vanilla invocations 
+- vanilla invocations
 - reset
 
 - set bands
 - priority invocations
 - sets private connection
-- priority invocations 
+- priority invocations
 - reset
 
 - set bands
 - sets client protocols
-- priority invocations 
+- priority invocations
 - sets private connection
-- priority invocations 
+- priority invocations
 - reset
 
 This test can be configured in several ways (72 to be precise) as
diff --git a/TAO/tests/RTCORBA/README b/TAO/tests/RTCORBA/README
index 18a3531b923..5c6cbf1dcab 100644
--- a/TAO/tests/RTCORBA/README
+++ b/TAO/tests/RTCORBA/README
@@ -5,7 +5,7 @@ for features defined in the RT-CORBA specification. Tests which exercise
 TAO-specific RT features can be found in $TAO_ROOT/performance-tests/RTCorba.
 OMG Real-time CORBA specification is available at:
 http://cgi.omg.org/cgi-bin/doc?ptc/99-05-03 (or check the OMG website
-for a more recent version).  
+for a more recent version).
 
 More information on TAO's implementation of RT-CORBA 1.0 specification
 is available at:
@@ -29,7 +29,7 @@ includes the following:
           Test for RTCORBA::ClientProtocol policy.
 
         . Collocation
-          
+
           Test for collocation when using thread pools and lanes.
 
         . Destroy_Thread_Pool
@@ -54,7 +54,7 @@ includes the following:
         . ORB_init
 
           Test for creation and destruction of multiple RT ORBs.
-          
+
         . Persistent_IOR
 
           Test for -ORBEndpoint option. Also makes sure that user
@@ -94,5 +94,5 @@ includes the following:
           Test for RTCORBA::ServerProtocol policy.
 
         . Thread_Pool
-        
+
           Tests the creation and use of thread pools.
diff --git a/TAO/tests/RTScheduling/Scheduling_Interceptor/README b/TAO/tests/RTScheduling/Scheduling_Interceptor/README
index 4f3d8e50831..c9fe2600475 100644
--- a/TAO/tests/RTScheduling/Scheduling_Interceptor/README
+++ b/TAO/tests/RTScheduling/Scheduling_Interceptor/README
@@ -1,4 +1,4 @@
-//$Id$
+$Id$
 
 Case
 ----
@@ -52,7 +52,7 @@ Server_Interceptor::send_reply
 Server_Interceptor::receive_request_service_contexts
 Server_Interceptor::receive_request
 Request from Distributable Thread
-The Guid is 1 
+The Guid is 1
 Two-Way Message = file:///project/ace/yamuna/ior_file
 Server_Interceptor::send_reply
 Distributable Thread - 1 is cancelled
@@ -66,7 +66,7 @@ Client
 
 Making a one-way request
 Client_Interceptor::send_request
-The Guid is 2 
+The Guid is 2
 Client_Interceptor::receive_other
 Making a two-way request
 Client_Interceptor::send_request
diff --git a/TAO/tests/TransportCurrent/IIOP/README b/TAO/tests/TransportCurrent/IIOP/README
index b340cfcab02..63b2d99d26a 100644
--- a/TAO/tests/TransportCurrent/IIOP/README
+++ b/TAO/tests/TransportCurrent/IIOP/README
@@ -1,6 +1,8 @@
+$Id$
+
 This test has two parts, which run automatically:
 
-Part 1: 
+Part 1:
 
 IIOP_Transport_Current test: Demonstrates how in the application the
 user can resolve the IIOP_Transport_Current and use it to obtain