[IGSTK-Users] Serial Communication problem in release

sebastian ordas sebastian.ordas at gmail.com
Fri Apr 11 14:24:19 EDT 2008


Hi Andinet,

actually, the serial communication test failed in released and worked fine
in debug

The polaris test does not check the return error value in
SerialCommunication::OpenCommunication

if you change:

if( !serialComm->OpenCommunication())
  {
      std::cout << "Serial port open failure\n";
      return EXIT_FAILURE;
  }

you can check yourself that only in debug works

find attached the new outputs

best regards,
Sebastian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080411/6a027ddc/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: RecordedStreamByPolarisTrackerTest4_Debug.txt
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080411/6a027ddc/attachment-0008.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: logPolarisTrackerTest4File_Debug.txt
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080411/6a027ddc/attachment-0009.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: RecordedStreamByPolarisTrackerTest4_Release.txt
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080411/6a027ddc/attachment-0010.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: logPolarisTrackerTest4File_Release.txt
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080411/6a027ddc/attachment-0011.txt>


More information about the IGSTK-Users mailing list