Problem after Cygwin update - bash hangs using 100% CPU
Simonz
I just updated Cygwin after a long time on my Win7 x64 system and to
my horror my favorite terminal in the world suddenly exhibits bizarre
behavior ...
I can start Terminator just fine and it executes my fairly long and
complicated .bashrc file and gives me a prompt. However a few short
commands later it will either hang while executing a command or
spontaneously execute. When it hangs there is a bash.exe taking 50%
CPU (all of a single core).
I can't reproduce this in the stock bash terminal, ONLY in
Terminator. It seems to relate somehow to output since the hang
always occurs when something gets output.
Anyone have thoughts about what's wrong and / or how I can further
diagnose it?
Cheers,
Simon
Martin Dorey
You received this message because you are subscribed to the Google Groups "terminator-users" group.
To post to this group, send email to terminat...@googlegroups.com.
To unsubscribe from this group, send email to terminator-use...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/terminator-users?hl=en.
Simonz
On Apr 3, 1:11 am, Martin Dorey <mdo...@bluearc.com> wrote:
> That's a new symptom, but at least two users, including me, couldn't use Terminator after upgrading to Cygwin 1.7.8. Downgrading just the "cygwin" component with "the clicky rotating thing" in setup.exe to 1.7.7 got me working again in mere seconds. Kenneth Wolcott's 1.7.8 mysteriously started working again, after he'd done various actions, like installing a snapshot, but then reverting it and upgrading perhaps other packages.
Unfortunately 1.7.7 is no longer available in the standard setup.exe,
it seems to have advanced to 1.7.9 as the latest version:
$ uname -a
CYGWIN_NT-6.1-WOW64 yeti 1.7.9s(0.236/5/3)
I guess I'll scrounge around and see if there's a way to get back to
1.7.7 through another avenue.
Cheers,
Simon
Martin Dorey
----- Original Message -----
From: terminat...@googlegroups.com <terminat...@googlegroups.com>
To: terminator-users <terminat...@googlegroups.com>
ArturoEA
Hi. I just installed a new machine yesterday with all of my usual free
software stack; it's a Windows 7 64-bits, UAC deactivated.
I have exactly the same symptoms; it's cygwin 1.7.9 I have installed.
Just to say that there may be a good bunch of users who are stumbling
upon this situation. I'll see what I can do about the downgrade.
In my case, ls will cause bash to hang, or not really. The funny thing
is that it doesn't happen if I keep myself on my home directory, but
does happen when doing it on /etc. So:
$ cd /etc; ls
will hang.
$ (cd /etc; ls)
will not hang.
$ cd /etc; echo *
will not hang.
I thought this had to do with the pwd, but how does that affect
terminator? Set PS1 to "$ " just in case it was the title setting
escape sequence, but the problem stays the same.
Greetings from Mexico!
Arturo
Martin Dorey
> I'll have to check out 1.7.9 on Monday, see if I can repeat this symptom.
I did and I still see the old symptom, eg:
13 [main] bash 4984 C:\cygwin-1.7\bin\bash.exe: *** fatal error - SetEvent failed
Stack trace:
Frame Function Args
0022AC78 6102796B (0022AC78, 00000000, 00000000, 00000000)
0022AF68 6102796B (6117EC60, 00008000, 00000000, 61180977)
0022BF98 61004F1B (611C4DA0, 00000000, 00000000, 00000000)
0022BFC8 610C75A2 (00020938, 00000000, 00000000, 00000000)
0022BFE8 61067D7D (611B5B7D, 00000001, 00000000, 00000000)
0022C018 61067EED (0022C044, 0022C020, 00000000, 00000000)
0022C198 61068E94 (00000000, 00000000, 00000000, 00000000)
End of stack trace
5 [main] bash 3064 C:\cygwin-1.7\bin\bash.exe: *** fatal error - SetEvent failed
Stack trace:
Ah, but I tried Arturo's insight, cd()d away from my home directory and, what do you know, bash hung 100%.
> There's some kind of Cygwin Wayback Machine or Cygwin Archive or something.
"Cygwin time machine". Man, I'd have never found that again, if I were not completely convinced that it existed.
http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine
Paste this into the New URL box, hit *Add* before Next:
ftp://www.fruitbat.org/pub/cygwin/circa/2011/02/25/154017
Bah, then it hangs for me, every time, at:
Then it tries uncompressed and that hangs too.
Well, a fat lot of use that is.
Simonz
>
> "Cygwin time machine". Man, I'd have never found that again, if I were not completely convinced that it existed.
>
> http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine
>
> Paste this into the New URL box, hit *Add* before Next:
>
> ftp://www.fruitbat.org/pub/cygwin/circa/2011/02/25/154017
>
> Bah, then it hangs for me, every time, at:
>
> Then it tries uncompressed and that hangs too.
>
> Well, a fat lot of use that is.
coverage is spotty. I wish I could remember which one worked for me.
I also remember connectivity wasn't that great but eventually it
worked and I am back with a completely functional Terminator. Fwiw,
there is also a highly important morsel of info that is buried deep in
the instructions that is easy to miss: you have to run Cygwin
setup.exe from a command line and give it the -X argument or it will
fail half way through checking signatures.
I agree this is going to become a big problem pretty soon as more and
more people happen to update Cygwin. I guess we wait and see if
patches going into Cygwin fix it but if Terminator is the only
application affected this way at some point we might have to consider
it "our" problem and try and fix it from Terminator's end. I'm up
for trying to help if it comes to that.
Ronald Pagani Jr
Regarding Cygwin 1.7.9...
Interesting, that you've gotten as far as you have. I believe I'm experiencing a similar issue (having also recently updated Cygwin, without intention joining the 1.7.9 bandwagon) although I'm not even able to get a successful launch.
Thinking it was my Terminator build, I upgraded to the latest and greatest release from software.jessies.org (Terminator 2.99.3250) without favorable consequence.
I dug around a bit, and found an installer debug build Martin provided here for an unrelated problem1, and witnessed the following:
$ /cygdrive/C/Program\ Files/software.jessies.org/terminator/Resources/terminator/bin/terminator
Running:
cygpath --windows '/cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/.generated/i386_Cygwin/lib'
3 [main] ruby 3256 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
3 [main] ruby 5424 fork: child 3256 - died waiting for dll loading, errno 11
1056840 [main] ruby 3192 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
1065065 [main] ruby 5424 fork: child 3192 - died waiting for dll loading, errno 11
2110707 [main] ruby 5292 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
2119120 [main] ruby 5424 fork: child 5292 - died waiting for dll loading, errno 11
3164623 [main] ruby 4108 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
3173480 [main] ruby 5424 fork: child 4108 - died waiting for dll loading, errno 11
4220958 [main] ruby 1200 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x330000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00330000)
End of stack trace
4226797 [main] ruby 5424 fork: child 1200 - died waiting for dll loading, errno 11
5272313 [main] ruby 2772 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
5283991 [main] ruby 5424 fork: child 2772 - died waiting for dll loading, errno 11
6334124 [main] ruby 5268 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
6354537 [main] ruby 5424 fork: child 5268 - died waiting for dll loading, errno 11
7403069 [main] ruby 4276 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
7425243 [main] ruby 5424 fork: child 4276 - died waiting for dll loading, errno 11
8473443 [main] ruby 5116 C:\cygwin_2_738\bin\ruby.exe: *** fatal error - unable to remap \\?\C:\cygwin_2_738\lib\ruby\1.8\i386-cygwin\etc.so to same address as parent: 0x340000 != 0x350000
Stack trace:
Frame Function Args
023FFF98 6102796B (023FFF98, 00000000, 00000000, 00000000)
02400288 6102796B (6117EC60, 00008000, 00000000, 61180977)
024012B8 61004F1B (611A7FAC, 61243A94, 00340000, 00350000)
End of stack trace
8494610 [main] ruby 5424 fork: child 5116 - died waiting for dll loading, errno 11
/cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:21:in ``': Interrupt
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:21:in `convert_to_jvm_compatible_pathname'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:35:in `pathnames_to_path'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:35:in `map'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:35:in `pathnames_to_path'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:260:in `add_pathnames_property'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:147:in `initialize'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/bin/terminator:83:in `new'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/bin/terminator:83:in `launch0'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/bin/terminator:21:in `launch'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:133:in `call'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:133:in `initialize'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:145:in `new'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/salma-hayek/bin/show-alert.rb:145:in `report_exceptions'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/bin/terminator:21:in `launch'
from /cygdrive/C/Program Files/software.jessies.org/terminator/Resources/terminator/bin/terminator:219
$ uname -a
CYGWIN_NT-5.1 WNCAASP021L 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
My attempts to investigate included a fresh install of Cygwin, which only confirmed the behavior above.
I thought I had an old Cygwin installer sitting around somewhere, at least I usually try to archive some tools, for these very instances.
Hopefully this gets sorted, it's painful without the use of my Dear, Dear Terminator. ;-)
1 From 2010-Aug-30, thread "[terminator-users] RE: Segfault"
<eom>
Ronald Pagani Jr
It's all over the web, I grabbed the following from this lucky person (`http://hundredthreads.blogspot.com/2010/03/cygwin-unable-to-remap.html')
For quick reference...
-- Exit all cygwin processes. Verify in Task Manager that there are no cygwin processes running.
-- Run 'cmd' from the run menu (Windows Key + R). Go to the cygwin bin directory and run ".\ash.exe".
-- Run "./rebaseall". This will take some time.
ArturoEA
posted.
Greetings,
Arturo
On Apr 14, 12:14 pm, Ronald Pagani Jr <contact...@net.ronpagani.com>
wrote:
> > from /cygdrive/C/Program Files/
> > software.jessies.org/terminator/Resources/salma-hayek/bin/invoke-java.rb:14 7:in`initialize'
> > from /cygdrive/C/Program Files/
> > software.jessies.org/terminator/Resources/terminator/bin/terminator:83:in`n ew'
> > from /cygdrive/C/Program Files/
> > software.jessies.org/terminator/Resources/terminator/bin/terminator:83:in`l aunch0'
> > from /cygdrive/C/Program Files/
> > software.jessies.org/terminator/Resources/terminator/bin/terminator:21:in`l aunch'
> > from /cygdrive/C/Program Files/
Martin Dorey
-----Original Message-----
From: terminat...@googlegroups.com [mailto:terminat...@googlegroups.com] On Behalf Of ArturoEA
Sent: Friday, April 15, 2011 08:40
To: terminator-users
Subject: [terminator-users] Re: Problem after Cygwin update - bash hangs using 100% CPU
Greetings,
Arturo
--
Martin Dorey
http://cygwin.com/ml/cygwin/2011-04/msg00185.html
But Ryan Johnson's test case, in http://cygwin.com/ml/cygwin/2011-04/msg00183.html, doesn't crash for me, from rxvt.
Austen
problem. have tried a rebaseall and downgrading the cygwin component
to 1.7.7 but still to no avail.
Thanks
On Apr 17, 9:34 pm, Martin Dorey <mdo...@bluearc.com> wrote:
> That didn't help, even once I rediscovered posix.dll and added that to the mix. I no longer think that we're completely alone. This suggests that even relatively simple programs can exhibit something that might be similar:
>
> http://cygwin.com/ml/cygwin/2011-04/msg00185.html
>
>
> read more »
Martin Dorey
Only Ken, and he doesn't know what he did.
> downgrading the cygwin component to 1.7.7 but still to no avail.
That's big news! We didn't know the bug (http://groups.google.com/group/terminator-users/browse_thread/thread/6a10d7cd43ee4460#) predated 1.7.8. How did you manage to downgrade it to 1.7.7? Although Simon suggested trying different dates (http://groups.google.com/group/terminator-users/browse_thread/thread/5b4e514602f795bd/7e68cc7c8ac306e2?lnk=gst&q=fruitbat#7e68cc7c8ac306e2) from the "Cygwin time machine", we don't have a record of a date that works.
Thanks
--
Kenneth Wolcott
Ken
Austen
re-ran setup and installed from local directory instead of the
internet.
When running 1.7.7 I didn't experience the same issue I got an error
relating to ___xpg_strerror_r instead. That may have been because I
needed to also downgrade other components. I didn't really have the
time to investigate fully.
At home I have terminator running absolutely fine (Haven't upgraded to
1.7.9 yet). That was fresh installed with setup version 2.738. When I
run setup again and view the packages pending upgrade I see that it
only wants to update the following:
cygutils 1.4.4-1 -> 1.4.6-1
cygwin 1.7.8-1 -> 1.7.9-1
rsync 3.0.7-1 -> 3.0.8-1
I'll try downgrading my broken cygwin install at work tomorrow to use
cygutils 1.4.4-1 and cygwin 1.7.8-1 see if that fixes it.
On May 3, 5:23 pm, Martin Dorey <mdo...@bluearc.com> wrote:
> > Has anyone found a solution to this?
>
> Only Ken, and he doesn't know what he did.
>
> > downgrading the cygwin component to 1.7.7 but still to no avail.
>
>
> read more »
Martin Dorey
That worked for me today, and "fixed Terminator". I'm not sure what I was doing wrongly before, though certainly I'd missed Simon's insight (thanks!):
> you have to run Cygwin setup.exe from a command line and give it the -X
> argument
I fear I may have made a second mistake: giving up on setup.exe too early. I only realized it worked because I left the Windows computer for a couple of minutes, to try to download setup.bz2 on another box. There's a much bigger pause, seemingly near the end of the download, with fruitbat that with <whatever my usual mirror is>.
-----Original Message-----
From: terminat...@googlegroups.com [mailto:terminat...@googlegroups.com] On Behalf Of Simonz
Sent: Wednesday, April 13, 2011 05:58
To: terminator-users
Subject: [terminator-users] Re: Problem after Cygwin update - bash hangs using 100% CPU
>
--
Martin Dorey
> relating to ___xpg_strerror_r instead.
If you're talking about a *build* issue there, then that's discussed here:
http://groups.google.com/group/terminator-users/msg/966560b2e68f8d5f
(It was fixed upstream thanks to "our" Ken.)
If you're talking about a runtime error, then that's news.
> I'll try downgrading my broken cygwin install at work tomorrow to use
> cygutils 1.4.4-1 and cygwin 1.7.8-1 see if that fixes it.
I just tried it and it didn't work for me.
...
But I did get fruitbat to work. I'll add you to that thread.
--
Austen
On May 4, 12:09 am, Martin Dorey <mdo...@bluearc.com> wrote:
> > When running 1.7.7 I didn't experience the same issue I got an error
> > relating to ___xpg_strerror_r instead.
>
> If you're talking about a *build* issue there, then that's discussed here:
>
> http://groups.google.com/group/terminator-users/msg/966560b2e68f8d5f
>
> (It was fixed upstream thanks to "our" Ken.)
>
> If you're talking about a runtime error, then that's news.
worked fine.
I've now tried to downgrade to 1.7.7 again today but for some reason
it no longer works, just doesn't install anything and cygwin fails to
execute with missing cygwin1.dll error.
>
> > I'll try downgrading my broken cygwin install at work tomorrow to use
> > cygutils 1.4.4-1 and cygwin 1.7.8-1 see if that fixes it.
>
> I just tried it and it didn't work for me.
>
> read more »
Martin Dorey
Oh yes:
---------------------------
ruby-launcher.exe - Entry Point Not Found
---------------------------
The procedure entry point __xpg_strerror_r could not be located in the dynamic link library cygwin1.dll.
---------------------------
OK
---------------------------
I removed the 1.7.9-compiled terminator.msi from the downloads directory, with the intention of replacing it with a 1.7.7 one, but it seems that my mingw gcc installation got trashed in the downgrade. It failed to build cygwin-launcher with errors like:
martind@vm-martind ~
$ g++.exe -mno-cygwin -x c /dev/null
/usr/bin/ld: cannot find crt2.o: No such file or directory
/usr/bin/ld: cannot find -lmingw32
/usr/bin/ld: cannot find -lmoldname
/usr/bin/ld: cannot find -lmingwex
/usr/bin/ld: cannot find -lmsvcrt
/usr/bin/ld: cannot find -lmingw32
/usr/bin/ld: cannot find -lmingw32
/usr/bin/ld: cannot find -lmoldname
/usr/bin/ld: cannot find -lmingwex
/usr/bin/ld: cannot find -lmsvcrt
collect2: ld returned 1 exit status
martind@vm-martind ~
$
The errors persisted after upgrade again. This was the key ingredient in fixing it:
$ ln -s /usr/lib/mingw /usr/i686-pc-mingw32/sys-root/mingw/lib
I had to create the sys-root directory.
After downgrade again, the problem, or a very similar one, came back, even though my hack was still there. The expedient hack there seems to be:
$ rmdir /usr/i686-pc-mingw32/lib
$ ln -s /usr/lib/mingw /usr/i686-pc-mingw32/lib
$
Finally, the latest msi should work again on 1.7.7... until something induces me to upgrade again.
(Most of this mail is for the benefit of future-me, but others might get Google hits (though Google seems recently less likely to show results from this mailing list: I have to try quite hard to find mails I know are here, or even to use the group's own Search).)
--
Steinar Haugen
Martin Dorey
> I guess you can add one to "gets this issue with cygwin 1.7.9 (windows 7, 64 bit) and rebase didn't work".
Thanks.
> it complains about some missing .sig files and then aborts
There's A Trick. You have to run setup.exe from the command line with -X.