From: David Dyck <david.dyck@gmail.com>
To: Mark Geisert <mark@maxrnd.com>
Cc: cygwin@cygwin.com
Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION
Date: Wed, 11 Aug 2021 07:25:41 -0700 [thread overview]
Message-ID: <CAJtSMgtPPT_8BAoYq2NDzuwog1xNt6wGkis2J1dwJyTMgkaD9w@mail.gmail.com> (raw)
In-Reply-To: <08cdda56-2994-ae30-d508-9491ad24422f@maxrnd.com>
First, thanks for digging further into this.
I'm guessing that I am missing some of the developer pieces that
assisted you in deducing from
On Tue, Aug 10, 2021 at 10:28 PM Mark Geisert wrote:
>
> Replying to myself, ahem...
>
> Mark Geisert wrote:
> > You could try downgrading ncurses via Cygwin setup. Best case: things work. Worst
> > case: things break but at a different address within the DLL.
>
> On another branch of this thread David reported that downgrading worked. We still
> don't know what the issue with current ncurses is, so I did try the following:
>
> > Another tack could be for somebody *on a working system* install the debuginfo for
> > ncurses, figure out the exception's address *in the ncurses installed locally*,
> > run 'more' under gdb after setting a breakpoint at that address. Poke around to
> > see what ncurses is doing in that area. Maybe it's acting on a Windows result
> > that's busted on the Windows preview. Or something else. Good luck with this
> > route :-/.
>
> Here's the gdb session from my own Windows 10 machine...
... thank you for looking at this in gdb
>
> That is all the help/damage I can do at this point.
> Cheers,
>
> ..mark
I started setup today and observed that the only "pending" actions
were a bunch of ncurses installs.
I clicked ok ( and enabled source just in case :-) ) and watched the
action begin.
Uninstall libncurses-devel 6.0-11.20170617 (automatically added)
Uninstall libncursesw10 6.0-11.20170617 (automatically added)
Uninstall ncurses 6.0-11.20170617 (automatically added)
Install libncurses++w10 6.1-1.20190727
Install libncurses++w10-src 6.1-1.20190727 (source)
Install libncurses-devel 6.1-1.20190727
Install libncurses-devel-src 6.1-1.20190727 (source)
Install libncursesw10 6.1-1.20190727
Install libncursesw10-src 6.1-1.20190727 (source)
Install ncurses 6.1-1.20190727
Install ncurses-src 6.1-1.20190727 (source)
both bash and more worked
( e.g. bash starts and more doesn't stack dump in this simple case
c:\cygwin64>cd bin
c:\cygwin64\bin>path c:\cygwin64\bin;%PATH%
c:\cygwin64\bin>which which
/usr/bin/which
c:\cygwin64\bin>more < NUL
c:\cygwin64\bin>
looking back at the downgrade log I see
Uninstall libncursesw10 6.1-1.20190727 (automatically added)
Uninstall ncurses 6.1-1.20190727 (automatically added)
so I think that I just upgraded to what I had before, not sure if
something was corrupted before.
I did search for ncurses in the cygcheck.out from before
$ ag -i ncurses cygcheck.out
1248: 301k 2019/07/28 c:\cygwin64\bin\cygncursesw-10.dll - os=4.0
img=0.0 sys=5.2
1249: "cygncursesw-10.dll" v0.0 ts=2019-07-28 09:30
1969:libncursesw10 6.1-1.20190727 OK
2132:ncurses 6.1-1.20190727 OK
next prev parent reply other threads:[~2021-08-11 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 4:36 David Dyck
2021-08-10 5:04 ` Brian Inglis
2021-08-10 5:16 ` David Dyck
2021-08-10 6:08 ` Brian Inglis
2021-08-10 14:20 ` David Dyck
2021-08-10 17:56 ` Brian Inglis
2021-08-10 18:20 ` David Dyck
2021-08-10 19:49 ` Mark Geisert
2021-08-10 20:30 ` Doug Henderson
2021-08-11 4:38 ` David Dyck
2021-08-11 5:27 ` Mark Geisert
2021-08-11 14:25 ` David Dyck [this message]
2021-08-12 5:09 ` Mark Geisert
2021-08-12 5:22 ` David Dyck
2021-08-10 5:07 ` Takashi Yano
2021-08-10 5:12 ` David Dyck
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=CAJtSMgtPPT_8BAoYq2NDzuwog1xNt6wGkis2J1dwJyTMgkaD9w@mail.gmail.com \
--to=david.dyck@gmail.com \
--cc=cygwin@cygwin.com \
--cc=mark@maxrnd.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).