This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Forked call
- From: Darryl Scott <darryls at productcosting dot com>
- To: <cygwin-xfree at cygwin dot com>
- Date: Mon, 19 Apr 2004 10:55:52 +0100
- Subject: Forked call
- Reply-to: cygwin-xfree at cygwin dot com
Hi!
I can find no input to this problem in the cygwin docs etc.
This problem does not occur if the Cygwin X server is used by the
executables that are compiled in SFU. It only happens when the executables
are Cygwin derived.
From X app 1 I call a simple fork programme using a system call. This fork
programme calls another X app using execv, the details of which have been
passed to it as arguments. The fork programme dies returning control to X
app1. The X app2 initiates and processes through all actions up to display.
It appears to pick up all the relevant X environment enquiries correctly.
Under SFU it progresses to display and operates as required. Under Cygwin
it dies, I have tried trapping signals but have found none.
This suggest that the X server is happy as it works with SFU and that the
problem is something I have to do with the cygwin generated X-app.
True, False or complete rubbish?
Input greatly appreciated.
Kind regards,
Darryl Scott
Profile Product Costing Ltd
The Old Vicarage, Market Place, Castle Donington, DE74 2JB, United Kingdom
Telephone: +44 (0) 1332 856972 FAX: +44 (0) 1332 810769 Mobile +44 (0)
7808 078388
Web : www.productcosting.com
This email and any attachments have been checked for viruses.