Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-11 Thread David Dyck via Cygwin 
On Wed, Aug 11, 2021 at 10:10 PM Mark Geisert  wrote:
>
> Hi David,
>
> David Dyck via Cygwin wrote:
> > 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
>
> No problem.  I was curious about the possible Win 11 Preview connection and
> happened to have a bit of free time to investigate.  Installing the
> ncurses-debuginfo package gave me debugging symbols for use with gdb.  
> Calculating
>  minus  from your strace gave me the 
> offset
> into the ncurses DLL of the exception on your system.  Then on my own system I
> have a different  but adding the offset gives me the
> corresponding  on my own system.  The rest was using gdb.
>

Thank you, I appreciate your contributing to my education.


> I didn't consider that your original libncursesw-10.dll might have been 
> damaged.
> I was kinda fixated on the possibility of Win 11 Preview brokenness ;-).


> That's right, you're back to the version you started with but things are 
> working
> now.  I'm now inclined to think your original ncurses DLL was damaged 
> somehow.  I
> don't know how deeply 'cygcheck -c' checks a package.. It can tell when 
> individual
> files are missing from the package but I don't know if it checksums the 
> files, for
> instance, to discover individual file damage.

Maybe there's an opportunity to have cygcheck include a checksum of
each file in its report - but too late now.

> I don't think there's anything more to do here but run your working system 
> :-).

Thank you, I am doing just that!
  David

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-11 Thread Mark Geisert 

Hi David,

David Dyck via Cygwin wrote:

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


No problem.  I was curious about the possible Win 11 Preview connection and 
happened to have a bit of free time to investigate.  Installing the 
ncurses-debuginfo package gave me debugging symbols for use with gdb.  Calculating 
 minus  from your strace gave me the offset 
into the ncurses DLL of the exception on your system.  Then on my own system I 
have a different  but adding the offset gives me the 
corresponding  on my own system.  The rest was using gdb.


[...]

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 :-/.


I didn't consider that your original libncursesw-10.dll might have been damaged. 
I was kinda fixated on the possibility of Win 11 Preview brokenness ;-).



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.


That's right, you're back to the version you started with but things are working 
now.  I'm now inclined to think your original ncurses DLL was damaged somehow.  I 
don't know how deeply 'cygcheck -c' checks a package.. It can tell when individual 
files are missing from the package but I don't know if it checksums the files, for 
instance, to discover individual file damage.


I don't think there's anything more to do here but run your working system :-).
Cheers,

..mark

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-11 Thread David Dyck via Cygwin 
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

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread Mark Geisert 

Replying to myself, ahem...

Mark Geisert wrote:

Hi David,

David Dyck via Cygwin wrote:

On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis  wrote:

Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find anything much useful from MS or articles only features.
You might want to reach out for help via the Windows Feedback Hub,
and/or MS App Assure re compatibility if your org has 150+ licenses.


I'm interested in what could be going wrong that would cause only some
cygwin programs to fail.

I'd be happy to report the issue via Windows Feedback if I could point
to something specific.

[...]
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...

/usr/lib/debug/usr/bin gdb -q more.exe
Reading symbols from more.exe...
(No debugging symbols found in more.exe)
(gdb) b main
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (main) pending.
(gdb) b ncwrap_cur_term   <-- I deduced the faulting func using exception 
address
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 2 (ncwrap_cur_term) pending.
(gdb) r
Starting program: /usr/bin/more.exe
[New Thread 12052.0x388]
[New Thread 12052.0x2750]
[New Thread 12052.0x2d08]
[New Thread 12052.0x275c]

Thread 1 "more" hit Breakpoint 2, ncwrap_cur_term ()
at /usr/src/debug/ncurses-6.1-1.20190727/ncurses/tinfo/lib_cur_term.c:68
68  return NCURSES_SP_NAME(_nc_get_cur_term) (CURRENT_SCREEN);
(gdb) disassem ncwrap_cur_term
Dump of assembler code for function ncwrap_cur_term:
=> 0x0003cc658a30 <+0>: mov0x18a39(%rip),%rax# 0x3cc671470 
<.refptr.SP>

   0x0003cc658a37 <+7>: mov(%rax),%rcx
   0x0003cc658a3a <+10>:jmp0x3cc658a10 <_nc_get_cur_term_sp>
End of assembler dump.
(gdb) list
63
64  NCURSES_EXPORT(TERMINAL *)
65  NCURSES_PUBLIC_VAR(cur_term) (void)
66  {
67  #if NCURSES_SP_FUNCS
68  return NCURSES_SP_NAME(_nc_get_cur_term) (CURRENT_SCREEN);
69  #else
70  return NCURSES_SP_NAME(_nc_get_cur_term) (NCURSES_SP_ARG);
71  #endif
72  }
(gdb) bt
#0  ncwrap_cur_term ()
at /usr/src/debug/ncurses-6.1-1.20190727/ncurses/tinfo/lib_cur_term.c:68
#1  0x0003cc65ac7c in _nc_setupterm (tname=0x80003a055 "xterm", Filedes=1,
errret=0xc4e4, reuse=0)
at /usr/src/debug/ncurses-6.1-1.20190727/ncurses/tinfo/lib_setup.c:646
#2  0x0001004057fd in ?? ()
#3  0x000180049cbb in dll_crt0_1 () at /oss/src/winsup/cygwin/dcrt0.cc:1037
#4  0x000180047736 in _cygtls::call2 (this=0xce00,
func=0x180048c40 , arg=0x0, buf=buf@entry=0xcdf0)
at /oss/src/winsup/cygwin/cygtls.cc:40
#5  0x0001800477e4 in _cygtls::call (func=,
arg=) at /usr/include/w32api/psdk_inc/intrin-impl.h:838
#6  0x in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

So the fault happens during ncurses initialization.  As to why this happens on a 
Win 11 Preview and evidently not on Win 10, I have no idea.  The code is trying to 
get the current value of 'cur_term', but that's not a local variable and I don't 
grok what the machine instructions are doing.  The fault address is the 2nd mov, 
so I believe the fault occurred during the 1st mov.


That is all the help/damage I can do at this point.
Cheers,

..mark

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread David Dyck via Cygwin 
On Tue, Aug 10, 2021 at 12:50 PM Mark Geisert wrote:
>

>
> You could try downgrading ncurses via Cygwin setup.  Best case: things work.

Best case achieved

Ran setup

this is what it said it would do

Uninstall libncursesw10 6.1-1.20190727 (automatically added)
Uninstall ncurses 6.1-1.20190727 (automatically added)
Install libncurses-devel 6.0-11.20170617
Install libncursesw10 6.0-11.20170617
Install ncurses 6.0-11.20170617

now I can click on my

   C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -

and get my beloved bash prompt again

Thank you all for getting me back up and running.
I am willing to try other experiments, though responses may be delayed at times.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread Doug Henderson via Cygwin 
On Tue, 10 Aug 2021 at 13:50, Mark Geisert  wrote:
>
> David Dyck via Cygwin wrote:
> > On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis  wrote:

Are you running any cygwin services? Be sure to stop them, and all
other cygwin processes before running cygwin setup.

Having any cygwin process running when you run setup may interfere
with the rebase. Likewise when you run the rebase all the process.

I saw some duplicate folders in your windows path. You don't need both
c:\WINDOWS\... and c:\Windows\... for example.


-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread Mark Geisert 

Hi David,

David Dyck via Cygwin wrote:

On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis  wrote:

Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find anything much useful from MS or articles only features.
You might want to reach out for help via the Windows Feedback Hub,
and/or MS App Assure re compatibility if your org has 150+ licenses.


I'm interested in what could be going wrong that would cause only some
cygwin programs to fail.

I'd be happy to report the issue via Windows Feedback if I could point
to something specific.

Maybe I should rebuild "more.exe" from source?


Won't help.  The strace and ldd output shows the exception is happening in 
cygncursesw-10.dll.  That's unfortunate because many Cygwin programs use that DLL, 
including the debugger gdb.



comparing the mentioned
   more.exe.stackdump
and
bash.exe.stackdump
it appears that cygwin creates different formats of files but seems to
call them *.stackdump


Yes, that's intentional.  Depending on the current state of the faulting program 
it may not be possible to get a stack backtrace.  The info shown is what can 
(probably) be trusted.


You could try downgrading ncurses via Cygwin setup.  Best case: things work. 
Worst case: things break but at a different address within the DLL.


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 :-/.


..mark

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread David Dyck via Cygwin 
On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis  wrote:

> Apparently that Windows Version is for the Windows 11 Preview.
> That appears to be an alpha quality product, from bug fix announcements.
> I didn't find anything much useful from MS or articles only features.
> You might want to reach out for help via the Windows Feedback Hub,
> and/or MS App Assure re compatibility if your org has 150+ licenses.

I'm interested in what could be going wrong that would cause only some
cygwin programs to fail.

I'd be happy to report the issue via Windows Feedback if I could point
to something specific.

Maybe I should rebuild "more.exe" from source?

comparing the mentioned
  more.exe.stackdump
and
   bash.exe.stackdump
it appears that cygwin creates different formats of files but seems to
call them *.stackdump

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread Brian Inglis 
On 2021-08-10 08:20, David Dyck via Cygwin wrote:> On Mon, Aug 9, 2021 
at 11:09 PM Brian Inglis  wrote:

> Microsoft Windows [Version 10.0.22000.120]


You may also want to check your Windows Preview release docs, and
articles about it, for features such as address changes or randomization
(e.g. ASLR) being experimentally enabled on some % of systems, or
mandated, and applied to dlls, which will break Cygwin.


thank you, I'll try to dig into the Windows Preview notes - as this
doesn't happen on the work laptop


Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find anything much useful from MS or articles only features.
You might want to reach out for help via the Windows Feedback Hub, 
and/or MS App Assure re compatibility if your org has 150+ licenses.


--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-10 Thread Brian Inglis 

On 2021-08-09 23:16, David Dyck via Cygwin wrote:

On Mon, Aug 9, 2021 at 10:04 PM Brian Inglis  wrote:

It's a known problem that after Windows updates, especially Insider,
quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to
rerun Cygwin Setup and allow packages to be upgraded in case patches are
made for new releases, and DLLs be rebased in case address space is
occupied by updated Windows components.


I did run cygwin setup, and it did not indicate any pending updates
that were required.
I'll try to do that more frequently, but now I am stuck, any other
ideas to try to get the tools running again


If you can, run "rebase-trigger full", or if you can't, run
"touch /var/cache/rebase/fullrebase" or do the equivalent with any tools 
available, then try rerunning Cygwin Setup, to see if that will 
stabilize your system.


You may also want to check your Windows Preview release docs, and 
articles about it, for features such as address changes or randomization 
(e.g. ASLR) being experimentally enabled on some % of systems, or 
mandated, and applied to dlls, which will break Cygwin.


--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-09 Thread David Dyck via Cygwin 
On Mon, Aug 9, 2021 at 10:04 PM Brian Inglis  wrote:

> It's a known problem that after Windows updates, especially Insider,
> quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to
> rerun Cygwin Setup and allow packages to be upgraded in case patches are
> made for new releases, and DLLs be rebased in case address space is
> occupied by updated Windows components.

I did run cygwin setup, and it did not indicate any pending updates
that were required.
I'll try to do that more frequently, but now I am stuck, any other
ideas to try to get the tools running again

would there be any clues offered from strace?  any other sources of information

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-09 Thread David Dyck via Cygwin 
On Mon, Aug 9, 2021 at 10:08 PM Takashi Yano wrote:
>
> On Mon, 9 Aug 2021 21:36:15 -0700
> David Dyck wrote:

> > I've had it running for many years, but recently upgraded to windows 10
> > c:\cygwin64\bin>ver
> >
> > Microsoft Windows [Version 10.0.22000.120]
>
> This does not seem to be a version number of Windows10 but
> a version number of latest Windows11 insider preview.
>
> However, in my environment, cygwin works as expected in
> Windows11 insider prevew as well as Windows10.

Yes, you are correct, it is Windows 11 insider preview
and I have another computer that is also running Win 11 preview with
cygwin just fine.
I was surprised to have these exceptions on what used to be a reliable system.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-09 Thread Takashi Yano via Cygwin 
On Mon, 9 Aug 2021 21:36:15 -0700
David Dyck wrote:
> I'm having trouble getting cygwin bash to start up - I tried older
> versions of bash, and I see that other tools are crashing also.  I'm
> looking for ideas on how to collect the useful information to begin
> the path to getting operation of cygwin restored.
> 
> I've had it running for many years, but recently upgraded to windows 10
> c:\cygwin64\bin>ver
> 
> Microsoft Windows [Version 10.0.22000.120]

This does not seem to be a version number of Windows10 but
a version number of latest Windows11 insider preview.

However, in my environment, cygwin works as expected in
Windows11 insider prevew as well as Windows10.

> seems like this computer ran cygwin bash probably in May of 2021.
> 
> To test cygwin tools I was able to add my cygwin bin directory to the path
> 
> c:\cygwin64\bin>path c:\cygwin64\bin;%PATH%
> 
> though normally I start cygwin with
>   C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -
> 
> 
> c:\cygwin64\bin>tcsh
>   0 [main] -csh 543 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to tcsh.exe.stackdump
> 
> c:\cygwin64\bin>fish
>   0 [main] fish 73 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to fish.exe.stackdump
> 
> c:\cygwin64\bin>bash
>   0 [main] bash 566 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to bash.exe.stackdump
> 
> c:\cygwin64\bin>zsh
>   0 [main] zsh 1146 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to zsh.exe.stackdump
> 
> # some shells start up
> 
> c:\cygwin64\bin>ash
> $ exit
> 
> c:\cygwin64\bin>dash
> $ exit
> 
> # even less crashes
> 
> 
> 
> c:\cygwin64\bin>.\date | less
>   1 [main] less 1907 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to less.exe.stackdump
> 
> ---
> on the other hand, many programs can give their initial help
> 
> c:\cygwin64\bin>bash --version
> GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> 
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> here is a sample stackdump
> 
> $ wc -l *.stackdump
>25 bash.exe.stackdump
> 9 fish.exe.stackdump
> 9 infocmp.exe.stackdump
>18 less.exe.stackdump
> 9 more.exe.stackdump
>28 python2.7.exe.stackdump
>25 sh.exe.stackdump
>33 tcsh.exe.stackdump
>22 zsh.exe.stackdump
>   178 total
> $ dash
> $ date | more
> Segmentation fault (core dumped)
> $ cat more.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at rip=003E07E8A37
> rax=0003EFB1A170 rbx=0001 rcx=00018037C76D
> rdx=0001 rsi=00018037C76D rdi=C514
> r8 =C514 r9 = r10=004D
> r11=0001004053BE r12= r13=CDF0
> r14= r15=
> rbp=0001 rsp=C448
> program=C:\cygwin64\bin\more.exe, pid 145, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B


-- 
Takashi Yano 

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION

2021-08-09 Thread Brian Inglis 

On 2021-08-09 22:36, David Dyck via Cygwin wrote:

I'm having trouble getting cygwin bash to start up - I tried older
versions of bash, and I see that other tools are crashing also.  I'm
looking for ideas on how to collect the useful information to begin
the path to getting operation of cygwin restored.

I've had it running for many years, but recently upgraded to windows 10
c:\cygwin64\bin>ver

Microsoft Windows [Version 10.0.22000.120]

seems like this computer ran cygwin bash probably in May of 2021.


It's a known problem that after Windows updates, especially Insider, 
quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to 
rerun Cygwin Setup and allow packages to be upgraded in case patches are 
made for new releases, and DLLs be rebased in case address space is 
occupied by updated Windows components.


--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple