From: Andy Wingo <wingo@pobox.com>
To: szgyg <szgyg@ludens.elte.hu>
Cc: 25912@debbugs.gnu.org
Subject: bug#25912: 2.1.7 segfaults on cygwin
Date: Wed, 01 Mar 2017 17:47:30 +0100 [thread overview]
Message-ID: <87a895djvh.fsf@pobox.com> (raw)
In-Reply-To: <20170301102709.GB4544@debbie.mshome.net> (szgyg@ludens.elte.hu's message of "Wed, 1 Mar 2017 11:27:09 +0100")
On Wed 01 Mar 2017 11:27, szgyg <szgyg@ludens.elte.hu> writes:
> I got two identical segfaults from make -j2 on 32-bit cygwin, and
> three identical segfaults from make -j3 on 64-bit at the same point.
>
> Any idea?
Could it be some mprotect issue? static-patch is a bytecode that is
used when doing run-time relocations in the .go files, when they are
first loaded up. They are loaded by loader.c. I usually use the mmap
path; is that being used on cygwin? Is it reliable? There is a
fallback path that doesn't use any memory protection. See loader.c.
Andy
next prev parent reply other threads:[~2017-03-01 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78221352.340980.1488551525340.ref@mail.yahoo.com>
2017-03-01 10:27 ` bug#25912: 2.1.7 segfaults on cygwin szgyg
2017-03-01 16:47 ` Andy Wingo [this message]
2017-03-02 9:13 ` szgyg
2017-03-06 19:41 ` Andy Wingo
2017-03-08 16:50 ` szgyg
2017-03-03 14:32 ` Mike Gran
2017-03-14 11:35 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a895djvh.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25912@debbugs.gnu.org \
--cc=szgyg@ludens.elte.hu \
/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).