This is the mail archive of the
mailing list for the Cygwin project.
Re: Cross-compiling Linux kernel
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Jun 2013 14:49:12 +0200
- Subject: Re: Cross-compiling Linux kernel
- References: <003401ce6b5d$f6ec87b0$e4c59710$%fedin at samsung dot com> <51BF7465 dot 2030104 at users dot sourceforge dot net> <001301ce6bf0$ea4904a0$bedb0de0$%fedin at samsung dot com> <20130618101706 dot GB27405 at calimero dot vinschen dot de> <003901ce6c1c$332722d0$99756870$%fedin at samsung dot com>
- Reply-to: cygwin at cygwin dot com
On Jun 18 16:06, Fedin Pavel wrote:
> While waiting for the Big Thing to finish compiling, another crazy idea visited my damaged brain. ;-) I wonder if it has some practical value...
> > That's not quite correct. The problem is not utilizing the native NT
> > functions to create a process image, the problem is that the Win32
> > libraries like advapi32, msvcrt, etc, which are directly or indirectly
> > loaded into a Cygwin process, are not capable to deal with a process
> > clone situation.
> So, in another words, we can clone everything except several known
> libraries. What if we use this fact ?
> Since we can create process image manually, what if we clone
> everything except these libraries ? Then we do a thing similar to
How would you do that? Either you use the native call to clone the
processes address space or you don't. If you clone, you get the
entire address space layout, including all DLL images and heaps
reserved by OS DLLs. These memory regions have to be free'd to be
able to reload the OS DLLs. How do you know which memory region
has been reserved by which OS DLL? Good luck implementing ;)
Btw., for reference:
> what we do now, we start the program from the beginning but tell it
> to follow "short path", attach missing libraries and jump to our
> Potential advantages:
> 1. clone'able DLLs (i assume that all Cygwin DLLs are cloneable) are
> guaranteed to get the same addresses.
> 2. (1) creates smaller number of variants for Windows native
> libraries, so we have smaller chances to get different addresses for
> Even more, what stops us from completely manual process image layout
> ? This way we could guarantee the same addresses for all libraries.
If you can get this working...
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple