public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: gjnospam2014-cygwinml@yahoo.com
To: cygwin@cygwin.com
Subject: Procmail stackdumps
Date: Thu, 20 Aug 2015 09:26:00 -0000	[thread overview]
Message-ID: <1440062636.14015.YahooMailBasic@web163406.mail.gq1.yahoo.com> (raw)

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

             reply	other threads:[~2015-08-20  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20  9:26 gjnospam2014-cygwinml [this message]
2015-09-10 11:17 ` D. Boland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1440062636.14015.YahooMailBasic@web163406.mail.gq1.yahoo.com \
    --to=gjnospam2014-cygwinml@yahoo.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).