public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: segfault on 32bit
Date: Tue, 7 Apr 2020 19:33:07 +0200	[thread overview]
Message-ID: <ca08d279-db91-b423-019f-e5df552e610b@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

while trying to build the 32bit version on python,
I hit this never seen before issue:

checking for %zd printf() format support... make: *** No targets 
specified and no makefile found.  Stop.
*** ERROR: make failed
       4 [main] sh 18479 D:\cygwin32\bin\sh.exe: *** fatal error in 
forked process - WFSO timed out after longjmp
       4 [main] sh 18479 D:\cygwin32\bin\sh.exe: *** fatal error in 
forked proces
s - WFSO timed out after longjmp
   72365 [main] sh 18479 cygwin_exception::open_stackdumpfile: Dumping 
stack trac
e to sh.exe.stackdump
   72365 [main] sh 18479 cygwin_exception::open_stackdumpfile: Dumping 
stack trac
e to sh.exe.stackdump


$ uname -svr
CYGWIN_NT-10.0-WOW 3.1.4(0.340/5/3) 2020-02-19 08:45

what is a WFSO ?
Attached stackdump.

Marco



[-- Attachment #2: sh.exe.stackdump --]
[-- Type: text/plain, Size: 120 bytes --]

Stack trace:
Frame     Function  Args
006DC438  61084F28 (00000148, 00000000, 00000000, 00000018)
End of stack trace

             reply	other threads:[~2020-04-07 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 17:33 Marco Atzeri [this message]
2020-04-07 20:27 ` Csaba Ráduly
2020-04-08  8:34   ` Dropping 32 bit Cygwin? (was Re: segfault on 32bit) Corinna Vinschen
2020-04-08  8:45     ` Corinna Vinschen
2020-04-08  8:53       ` Sharuzzaman Ahmat Raslan

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=ca08d279-db91-b423-019f-e5df552e610b@gmail.com \
    --to=marco.atzeri@gmail.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).