Re: msvc based X dlls and fork

["Victor Polsky" <victor at hcl dot com>]

Yes, I have a cygwin-compiled application doing X-stuff through a
ms-compiled dll, to be exact
Exceed XDK dlls. xterm crashes during initialization when trying to create
child process by calling fork.
My question is: why fork does not copy data from parent to child process
properly?
I know that xterm developed with xfree86 works which means fork works fine,
but I'd prefer XDK.
How I see the problem: Xt is not a dll in xfree86 but static library, in XDK
it's a dll, and all widget stuff
is created there. So, it's well known problem of MS dlls with so-called
extra pointer to data.
MS __decspec(import) mechanism resolves it, but what about CYGWIN32?

Victor.


-----Original Message-----
From: Andrew Markebo <flognat@flognat.myip.org>
To: Victor Polsky <victor@hcl.com>
Cc: cygwin@cygwin.com <cygwin@cygwin.com>
Date: Monday, April 02, 2001 11:43 AM
Subject: Re: msvc based X dlls and fork


>I am having a small problem seeing the area around the problem. You
>have a cygwin-compiled application doing X-stuff through a ms-compiled
>dll, or??
>
>What is the xterm doing?
>
>You maybe should give the X-libraries compiled with cygwin a try?
>        http://xfree86.cygwin.com/
>
>        /Andy
>
>/ "Victor Polsky" <victor@hcl.com> wrote:
>| Hi,
>|
>| I have found that when I use X dlls built with msvc (not gcc) all
structures
>| created inside the dlls (Display for example) cannot be used in child
>| process created by fork. The app (xterm) will crash inside child process.
I
>| can see correct pointer to structure in the child but inside the
structure
>| some junk.
>| Could anybody tell me what's wrong or what I did wrong to have it?
>| Maybe it's some compiler or linker flag I missed?
>|
>| Thanks, Victor.
>|
>|
>|
>|
>|
>| --
>| Want to unsubscribe from this list?
>| Check out: http://cygwin.com/ml/#unsubscribe-simple
>


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple