This is the mail archive of the 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: mark_closed messages

On Sun, Jul 07, 2002 at 03:37:40PM +0100, Conrad Scott wrote:
>AFAICT (and this was all new to me, so I may be utterly adrift
>here), the difficulty is that the child process needs to create
>and protect handles *before* the parent's data space is copied
>down into it.  So, the child would need to keep a temporary list
>of protected handles and merge these into the list it inherited
>from the parent once it had access to it.  Not impossible but not
>my cup of tea today.

Thanks for the analysis.  I'll incorporate some of your ideas into but I have to think about the clexec stuff.  I must have
changed the handle list to NO_COPY at some point which caused
some of these problems.

It sounds like the handle list is a candidate for the cygheap, so
that it can be properly dealt with in execed and forked processes.

Of course, maybe we should just nuke the whole concept, too.  I
think the vast majority of "problems" that the ProtectHandle stuff
has unearthed have been "false positives", lately.


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