X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=UXFNgtiNHqoEOnsU yiN2HgcmtZSl3ukYjih2n4PlUJJiJXL3stHvOb51Oi1Ok27PtK1ltsVwxUK4MkXe 5EivDu3VnI8Pw63yAjL8ECbOgcS0EatS7f97sYPQEHLY5xsRlcuK0B9u+G0lTIV/ zV7uVa2cr4AA93Up+RSGiRd6F9c= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=dXzn4CDAJeWLwpkHyhIBZr 771UI=; b=L44ndLPnqgkvWLTSLDKHLQUW48Sz+gs5Gk4OQjobQTcf7GKG3XLtPS UcC++97VvsJeE/82ncTARCN1PQQbK8Cuwk8YR7v0/yewpkbmK4G6dwbAg0BRTYND yKbQIrEMOCIy4pd51Y5ipTc94tI+J0Q7bCyHa/Buh8NppFJjnv9UM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.4 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=stack-allocated, stackallocated, Might, H*RU:!192.168.1.100! X-HELO: m0.truegem.net Subject: Re: crash caused by stack-allocated array in child process after fork? To: cygwin AT cygwin DOT com References: <57016B18 DOT 6030906 AT towo DOT net> From: Mark Geisert Message-ID: <57019C31.8060006@maxrnd.com> Date: Sun, 3 Apr 2016 15:41:53 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <57016B18.6030906@towo.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Thomas Wolff wrote: > Might it be related to > https://cygwin.com/ml/cygwin-developers/2016-03/msg00000.html ? I can only comment on this last sentence. Although I was seeing a particular function declared as a constructor being run twice, I was confused about the timing (due to not properly flushing log messages). With proper logging, I saw that both constructor runs were in the parent process and had nothing to do with that parent later forking. ..mark -- 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