From: Mike Gran <spk121@yahoo.com>
To: "25912@debbugs.gnu.org" <25912@debbugs.gnu.org>
Subject: bug#25912: 2.1.7 segfaults on cygwin
Date: Fri, 3 Mar 2017 14:32:05 +0000 (UTC) [thread overview]
Message-ID: <78221352.340980.1488551525340@mail.yahoo.com> (raw)
In-Reply-To: <20170301102709.GB4544@debbie.mshome.net>
Hi-
I also can replicate the Cygwin problem as originally described.
After wingo's comment on the mmap path vs the non-mmap path,
I tried to use the non-mmap path by removing HAVE_SYS_MMAN_H
from the config.h.
The non-mmap path doesn't build. The errors are in map_file_contents()
in loader.c
Making the obvious patches to map_file_contents() does
seem to allow the Cygwin build to continue.
The helper functions sniff_elf_alignment and copy_and_align_elf_data
are no longer included in master and had to be pulled from an older
rev.
Regards,
Mike
next prev parent reply other threads:[~2017-03-03 14:32 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
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 [this message]
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=78221352.340980.1488551525340@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=25912@debbugs.gnu.org \
/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).