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:message-id:date:from:reply-to:subject:to :mime-version:content-type; q=dns; s=default; b=XRO6jUFZu3uVrgfc C/FMXHyklOZ7hvhigTuj7rdfcBh62ST7tzcvru6NNP5KxgtWFstLo5KBTMKAbZw/ 2T+O2Opzs9u3jum2P9GTwQeywLiow2CYm+UkkDwtG+XiTESXER6UNgDUmRqAvrpA QTsNAy9fu7Cpsy6e+U6jjGzB6W8= 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:message-id:date:from:reply-to:subject:to :mime-version:content-type; s=default; bh=8bwTY2rnmyMacM5earBMg5 F9ZCY=; b=PsR5C0hb9nxXxXf/3/Jwo+doNHOIyYB4nJNwkpwEhTuayr+7icArX8 FAQEkszaBXkJeNOdCpSA2cqKU99EDen6Cs7B6uwmbtkrCODPpsZf/ZkuJDWbxf5t 6HCVdJ2HLG/T1r/6r2vS4zN1bC2jujJng2fOLIWSMQ82RzQNyiYuA= 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=-0.5 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: nm31-vm10.bullet.mail.gq1.yahoo.com Message-ID: <1440062636.14015.YahooMailBasic@web163406.mail.gq1.yahoo.com> Date: Thu, 20 Aug 2015 02:23:56 -0700 From: gjnospam2014-cygwinml AT yahoo DOT com Reply-To: gjnospam2014-cygwinml AT yahoo DOT com Subject: Procmail stackdumps To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 -- 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