This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Why are the 32- and 64-bit cygwin1.dlls incompatible?


On Thu, Aug 22, 2013 at 1:14 PM, Corinna Vinschen wrote:
>
> When execveing a Cygwin process, a lot of data is submitted via shared
> memory, via data copying, and via a special parameter to the
> CreateProcess call with the mysterious name "lpReserved2".
>
> One problem is the differences in basic datatypes, which results in
> incompatible datastructures between 32 and 64 bit.  While this could be
> worked around, this doesn't help for the shared memory stuff, which
> depends on the installation path of the cygwin DLL.  The Cygwin DLL in
> C:\cygwin1 would use a different name for the shared mem regions than
> the Cygwin DLL installed into C:\cygwin2, independent of the target
> architecture.  This is by design since Cygwin 1.7.  One effect:  No tty
> sharing.
>

Since you know that the DLL regions are different what about execing
the process as if it were a windows native process?  I know you loose
the ability to do the parent/child relationship but it isn't any worse
than spawning a native process.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]