This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Handling XWin.exe with Namedpipes for IPC with und generated Windows Program (Win-32 PE .EXE)
- From: <choice15 at gmx dot de>
- To: <cygwin-xfree at cygwin dot com>
- Date: Thu, 24 Oct 2002 15:11:57 +0200
- Subject: Handling XWin.exe with Namedpipes for IPC with und generated Windows Program (Win-32 PE .EXE)
- Organization: choice15@gmx.de
- References: <3DB7B360.1010508@gmx.de> <87d6q0auq2.fsf@vzell-de.de.oracle.com>
- Reply-to: cygwin-xfree at cygwin dot com
- Reply-to: <choice15 at gmx dot de>
Hi,
Is there an Difference between the XWin.exe (or any other Cygwin compiled
Binaries) and
MS Visual C/C++ oder Borland C Executables?
I experimenting the handling of XWin.exe vCommandline Arguments via
Namedpipes
but on Access to the Process my MS C or Borland C Programm is teminating
with a
Access Violation (Windows Programms like ping.exe works fine?)
Is there an Problem to handle Cygwin binaries via Named Pipes from "normal"
Windows 32 Portable Excutable?
Greetings