porting woes...

New Message Reply Date view Thread view Subject view Author view

jparsons++at++ist.ucf.edu
Wed, 30 Oct 1996 01:30:19 -0500


Performers:

  I am porting some 1.2 code to Performer 2.0 on an Onyx RE2
  running IRIX 5.3. The only significant changes I have made to
  what has been reliable code, is converting from Pipes to PWins. I
  now find that if I instance an Ascension driver class that opens a
  serial port for reading and writing *before* I make my first
  pfFrame() call, then I am unable to read data from the port.
  However, as long as I wait until after the first pfFrame (wherever
  in the code I happen to choose to put it) everything works just
  dandy.

  Is there a connection between pfFrame and proper access to a port,
  or is this just an ugly memory leak, as I suspect, that has reared
  its head now that the code segments have been shuffled?

  BTW, I am using system read and write calls to the port, and opening
  it from my own non-Performer (time-tested) serial class. This behavior
  occurs whatever the proc split happens to be.

  Ideas appreciated...

  Jim Parsons
  Visual Systems Lab
  Institute for Simulation & Training
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:50 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.