DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=qMPGZFQ40BRGrVs9zJLjYeu8an5KWwK1LebEPOvqKHL
	pZDHqP32ziiYBeK7kdRly/pwdtypRTPn0+VjS9avLfGHra3KNNTuGCnCeUtU3mqD
	ZvTNNpShbYZksNIcgmuGLW6BdH0MMgreL2+EpRlM1EfdeHzsyCwl5l0lAZ3FCqps
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <52D63CE2.9060308@lysator.liu.se>
Date: Wed, 15 Jan 2014 08:46:42 +0100
From: Peter Rosin <peda@lysator.liu.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: fork() + file descriptor bug in 1.7.27(0.271/5/3) 2013-12-09 11:54
References: <831845.98759.bm@smtp116.sbc.mail.ne1.yahoo.com>	<52D55D96.8070407@redhat.com>	<946338.89157.bm@smtp116.sbc.mail.ne1.yahoo.com> <CAG9p0OR8JYgC1rzBCn1bvXe5ffpJS3vpmnnxw-7brJi8E8+uhQ@mail.gmail.com>
In-Reply-To: <CAG9p0OR8JYgC1rzBCn1bvXe5ffpJS3vpmnnxw-7brJi8E8+uhQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 2014-01-15 05:53, Lord Laraby wrote:
> On Tue, Jan 14, 2014 at 10:50 AM, Ted Nolan wrote:
>> In message <52D55D96.8070407@redhat.com> you write:
>>>
>>> Your program may be violating POSIX, which would trigger undefined behavior.
>>>
>>> Quoting POSIX:
>>> pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html#tag_15_05
>>>
>>
>> [long quote elided]
>>
>> Yikes!  That's pretty impenatrable.  And if it says what I think it says,
>> it seems to violate the way I've understood Unix fork() and how fds
>> (and stdio buffers) are inherited since forever.
>>
>> However..
>>
>> Do I understand that to say that if the first thing my child does is
>>
>>         fclose(fp);
>>
>> everything should be hunky-dory?
>>
>> Because I just tried that, and it's still not.
> 
> My two cents say, since the child is not referencing 'fp' at all,
> there is no violation of the POSIX semantics in this situation. It
> actually does seem, however, that the fork is closing, or at least
> forgetting the stdio file position of, fp when it forks. A possible
> memory corruption during fork from which fgets can not recover?

Let me requote one little bit quoted by Eric:

	                           (If the only action performed by one of the
	processes is one of the exec functions or _exit() (not exit()), the
	handle is never accessed in that process.)

Ted is using exit() in the children, not _exit(), and the above indicates
that exit() in fact "accesses the handle". My guess would be that fclose(3)
also "accesses the handle".

But, reading about _exit(), it seems that handle accesses are implementation
defined, so I'm not sure it will help in all situations.

Cheers,
Peter


--
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