From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: Fork problem with hexchat if cygserver is running
Date: Wed, 07 Aug 2019 17:41:00 -0000 [thread overview]
Message-ID: <d9f9e3b4-23ff-d5ae-d0b9-26f6ab752c7a@cornell.edu> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2180 bytes --]
Roughly 1 out of 3 times that I try to use hexchat, I get a fork failure:
31143510 [main] hexchat 12392 dofork: child 12399 - died waiting for dll
loading, errno 11
It only happens if cygserver is running. I caught it under strace and saw the
following:
29 25558 [main] hexchat 12399 frok::child: hParent 0xAF0, load_dlls 1
43 25601 [main] hexchat 12399 open_shared: name cygpid.12392, n 12392,
shared 0x1100000 (wanted 0x0), h 0x10C, *m 6
35 25636 [main] hexchat 12399 getpid: 12399 = getpid()
65 25701 [main] hexchat 12399 transport_layer_pipes::connect: Try to
connect to named pipe: \\.\pipe\cygwin-e022582115c10879-lpc
363 26064 [main] hexchat 12399 C:\cygwin64\bin\hexchat.exe: *** fatal error
in forked process - fixup_shms_after_fork: NtMapViewOfSection (0x7FF4EE130000),
status 0xC0000018. Terminating.
[status 0xC0000018 is STATUS_CONFLICTING_ADDRESSES.]
This was under cygwin-3.0.7-1. It also happens with cygwin1.dll built from the
current master branch, and it also happens with cygwin-3.0.6-1. Not being
familiar with this part of the Cygwin code, my first thought was to do a
bisection. But I haven't yet found a good revision to start with. I will still
try to do that, but in the meantime I thought I should report it.
Here are the reproduction instructions:
1. Start the cygserver service.
2. Start the X server. (I do this by using the XWin Server shortcut, which
basically just calls startxwin.)
3. Start xterm, and run 'hexchat &'.
4. Select the freenode network and click Connect.
Roughly 1 out of 3 times, the dofork error will print in the xterm window, and
hexchat will hang at "Looking up chat.freenode.net".
Ken
P.S. File this under "No good deed goes unpunished." I was trying to use
hexchat to join #cygwin-developers. I can still do that on 2 out of 3 attempts,
but now I'm sidetracked trying to do a bisection.
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next reply other threads:[~2019-08-07 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 17:41 Ken Brown [this message]
2019-08-07 18:46 ` Achim Gratz
2019-08-08 7:27 ` Michael Haubenwallner
2019-08-08 8:24 ` Corinna Vinschen
2019-08-08 8:57 ` Corinna Vinschen
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=d9f9e3b4-23ff-d5ae-d0b9-26f6ab752c7a@cornell.edu \
--to=kbrown@cornell.edu \
--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).