From: Jeremy Drake <cygwin@jdrake.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@Shaw.ca>
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls /proc/PID/...
Date: Sun, 1 Jan 2023 10:51:13 -0800 (PST) [thread overview]
Message-ID: <alpine.BSO.2.21.2301011047470.28808@resin.csoft.net> (raw)
In-Reply-To: <1253ac7c-12bc-d6db-9f83-3d950b03b30a@Shaw.ca>
On Sat, 31 Dec 2022, Brian Inglis wrote:
> was also getting the messages below locally and still on GitHub scallywag:
>
> cygcheck (6936) child_copy: cygheap read copy failed,
>
> ../curl/scallywag/1_x86_64 build.log:2022-12-26T00:39:35.6163236Z 0
> [main] cygcheck (6936) child_copy: cygheap read copy failed, 0x0..0x80003B5F0,
> done 0, windows pid 6936, Win32 error 299
> ../curl/scallywag/1_x86_64 build.log:2022-12-26T00:48:03.4525278Z 0
> [main] cygcheck (568) child_copy: cygheap read copy failed, 0x0..0x80003BA48,
> done 0, windows pid 568, Win32 error 299
> ../dialog/scallywag/1_x86_64 build.log:2022-12-31T18:42:37.0939902Z 0
> [main] cygcheck (6992) child_copy: cygheap read copy failed, 0x0..0x80003CB38,
> done 0, windows pid 6992, Win32 error 299
This feels ASLR related. Maybe try what Corinna suggested in
https://cygwin.com/pipermail/cygwin/2022-December/252720.html for a
similar error in Docker?
> Try this:
>
> cp /bin/cygwin1.dll ~/docker-cygwin1.dll
> peflags -d0 ~/docker-cygwin1.dll
>
> Then copy that DLL over to /bin/cygwin1.dll in your docker image
> and try again.
Though of course disregard 'docker' there.
next prev parent reply other threads:[~2023-01-01 18:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 20:01 Brian Inglis
2023-01-01 18:51 ` Jeremy Drake [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-30 4:59 Brian Inglis
2023-01-02 2:32 ` Takashi Yano
2023-01-02 5:38 ` Takashi Yano
2023-01-02 8:21 ` Takashi Yano
2023-01-09 13:20 ` Corinna Vinschen
2023-01-16 9:02 ` Takashi Yano
2023-01-16 10:23 ` Corinna Vinschen
2023-01-16 14:45 ` Takashi Yano
2023-01-16 15:18 ` Corinna Vinschen
2023-01-16 19:23 ` Brian Inglis
2023-01-16 21:42 ` Corinna Vinschen
2023-01-17 20:46 ` Corinna Vinschen
2023-01-18 9:16 ` Takashi Yano
2023-01-18 9:42 ` Corinna Vinschen
2023-01-19 16:31 ` Brian Inglis
2023-01-19 17:12 ` Brian Inglis
2023-01-19 18:38 ` Corinna Vinschen
2023-01-19 18:42 ` Jose Isaias Cabrera
2023-01-19 19:31 ` Brian Inglis
2023-03-21 19:17 ` Brian Inglis
2023-03-22 19:05 ` Brian Inglis
2023-01-02 23:03 ` Takashi Yano
2023-01-09 16:02 ` Corinna Vinschen
2023-01-09 17:13 ` Corinna Vinschen
2023-01-10 10:01 ` Takashi Yano
2023-01-10 10:57 ` Corinna Vinschen
2023-01-09 13:36 ` Corinna Vinschen
2023-01-10 0:00 ` Brian Inglis
2023-01-16 15:40 ` Jon Turney
2023-01-16 18:54 ` Brian Inglis
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=alpine.BSO.2.21.2301011047470.28808@resin.csoft.net \
--to=cygwin@jdrake.com \
--cc=Brian.Inglis@Shaw.ca \
--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).