DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=OiolPYKU28ViTMGp03ocA3D3uqXQMw
	lQaruXHNfONqQKiQeiUPR6WdsVug95Tf8+X+NFRy3NvK/NPOlF/dP7B+H6qAoeQH
	9CZaDJuXZX58eYFmWk6QToFZu/oHVcWKIPWnGQRnt4ZmBvh/Yszu2kZcA0t9O7ok
	XmTh/kH8T/bkg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: "D. Boland" <dboland AT xs4all DOT nl>
Subject: Re: Procmail stackdumps
Date: Thu, 10 Sep 2015 13:28:58 +0200
Lines: 60
Message-ID: <msrorf$5be$1@ger.gmane.org>
References: <1440062636 DOT 14015 DOT YahooMailBasic AT web163406 DOT mail DOT gq1 DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
In-Reply-To: <1440062636.14015.YahooMailBasic@web163406.mail.gq1.yahoo.com>

gjnospam2014-cygwinml AT yahoo DOT com schreef op 20-8-2015 om 11:23:
> Hi,
>
> I have a problem with a procmail recipe which previously worked but now doesn't, and causes procmail to generate a stackdump.
>
> :0
> #  * ^Subject:.* something or other
> {
>    :0 BW
>    * ^KeyWord
>    {
>      :0 b
>      NUM_FOUND=|${PMD_DIR}/numOfMatches
>
>      :0 b
>      SEARCH_NAME=|${PMD_DIR}/searchName
>    }
>
> #   :0 hfw
> #   | $FORMAIL -i "Subject: $SEARCH_NAME found $NUM_FOUND_FOUND matches"
> }
>
> Interestingly, each of the recipes in the inner block works perfectly individually (i.e. if I comment out the other one), but when they follow one another like that I get the following in my procmail log:
>
>        2 [main] procmail 1812 fork: child -1 - forked process 468 died unexpectedly, retry 0, exit code 0xC000012D, errno 11
> 16015111 [main] procmail 1776 fixup_mmaps_after_fork: ReadProcessMemory failed for MAP_PRIVATE address 0x7FDF9060000, Win32 error 998
> 16017947 [main] procmail 1776 C:\cygwin64\bin\procmail.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed
> 16020300 [main] procmail 1776 cygwin_exception::open_stackdumpfile: Dumping stack trace to procmail.exe.stackdump
> 16084774 [main] procmail 1812 fork: child -1 - forked process 1776 died unexpectedly, retry 0, exit code 0x100, errno 11
> procmail: Terminating prematurely whilst waiting for fork
>    Folder: **Bounced**							      0
>
> but only after waiting an inordinately long time and applying ctrl-c to procmail.
>
> The stackdump file is created before that, I can see that happening, and contains:
> Stack trace:
> Frame        Function    Args
> 0000022F368  0018007201E (001802110C0, 00180210E86, 00000008000, 0000022E1F0)
> 0000022F368  00180046EA2 (0000022F258, 001801E4EF0, 0000022FB00, 0000022F368)
> 0000022F368  00180046EE2 (00000000000, 0000022EF38, 00000008000, 001004102A8)
> 0000022F368  00180047454 (00000000002, 00180040000, 00180040000, 00000000000)
> 0000022F368  00180048920 (001004183AC, 00100418DD4, 0000022F358, 000778DFFFC)
> 0000022F368  001800C62E9 (00077A9B799, 000003A2C20, 000003A27B0, 000003A27B0)
> 00077B65468  00077A9B108 (00000000000, 0000022F490, 00000000000, 00000000000)
> 00077B65468  00077AA1E5A (00077AA4071, 0000022FB00, 00000000000, 00000000000)
> 00000000000  00077AA1937 (00000000000, 7FFFFFD7000, 00000000000, 00000000000)
> 00000000000  00077A8C34E (00000000000, 7FFFFFD7000, 00000000000, 00000000000)
> End of stack trace
>
> Even if I put the recipes into separate blocks (still within the outer block, but in two separate blocks) the problem occurs.  I'm baffled.
>
> Yours, sincerely,
> Baffled
>
Hi Baffled,

Sorry for the delay. I'll look into it.

Daniel


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