[Bug 4478] New: inter-proc comms issue

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=4478

Summary: inter-proc comms issue
           Product: Wine
           Version: 0.9.7.
          Platform: PC
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

I installed Wine 0.9.6 and then 0.9.7 on Ubuntu 6.04. I configured Wine 
with pure winecfg. Setup OK (seems). Windows apps such
as firefox runs with Wine. I am particularly interested in getting a
couple Chinese financial software to run successfully and will make me
fully unload Windows.

At the moment they run, but have a couple problems. It seems to me the
problems only have to do with inter-proc comms. With one program for
instance, the main process and the data receiving child process both run
and I can tell that the data-receiving process does connect and receive
data (real-time stock data) from the Internet, but the main process can
not see the data received. There are times when the main process
instructs the child process to get more data, but it seems in Wine the
child process does not get the instruction.  There is not much error
information in the xterm where I started wine. I know on Windows the
program uses memory mapping and so I guess the inter-proc comms is
achieved through memory mapping. I did check with pmap on Ubuntu and
found that there are some memory mapped with the two processes, though I
couldn't tell if they are mapped correctly.  My question is how does
Wine support inter-proc comms, or how can I further detect or ensure
about the inter-proc comms? Can it be achieved by simply copying some
dlls, and if so, how do I determine which dlls I would need?