non-printable characters sent or received with vtkErrorMacro
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
in client server mode when server errors are reported in the terminal a number of non-printable chars are streamed out. This is usually an indication of reading uninitialized memory. To reproduce you need to generate a server side error, one way to do it is to trump up a "text.bov" file, the visit bridge will choke on it and report an error.
pasting below (hope the non-printable chars come along for the ride):
�t�� ERROR: In /scratch/01237/bloring/ParaView/next/ParaView/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 751 vtkPVCompositeDataPipeline (0x240ae70): Algorithm vtkVisItBOVReader(0x23f8e70) returned failure for request: vtkInformation (0x242ab30) Debug: Off Modified Time: 152125 Reference Count: 1 Registered Events: (none) Request: REQUEST_DATA_OBJECT ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0