read() across network corrupting memory?

Hello. I am now successfully spawning components of our app onto remote
nodes, and things are mostly working. However, we are now seeing memory
corruption on the remote components. I tracked the problem down to a
read() call in flex-generated code. A coworker and I both have vague
recollections from posts on the QNX discussion groups that there is a known
bug in 6.2.1 applying to read() calls that go across QNET. I’ve been
unable to turn up anything with Google or the QNX knowledge base. Does
anyone else remember anything like this? Thanks.

I’ll try to generate a smaller program that illustrates this today.

Josh Hamacher
FAAC Incorporated