Re: Emacs crashing after M-x compile after Cygwin updates
Bruce Mardle via Cygwin writes: > Hi, all. I've been happily compiling simple C programs under Emacs > (emacs-w32) under Cygwin. Yesterday I wanted to install > libedit-dev. While I was doing that, setup...exe marked a few dozen > other packages for upgrades. I didn't notice which. You can still find that out today by looking at /var/log/setup.log and (for the immediately prevuious run of setup.exe) in much more detail in /var/log/setup.log.full -- so do not start setup.exe again in case you think there might be something you need to check in detail before copying that file someplace safe. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: Emacs crashing after M-x compile after Cygwin updates
On Mon, 4 Apr 2022 13:08:27 + (UTC) Bruce Mardle wrote: > Hi, all. > I've been happily compiling simple C programs under Emacs (emacs-w32) under > Cygwin. Yesterday I wanted to install libedit-dev. While I was doing that, > setup...exe marked a few dozen other packages for upgrades. I didn't notice > which. Now, if I `emacs hello.c` and M-x compile gcc -o hello hello.c the > compilation works... but then, a few seconds later, Emacs SEGVs. emacs-nox > does the same but without the delay. > I've tried Emacs versions 27.2-1, 28.0.60-1.f7e6c199bf, and 27.1. Then, in > case it was gcc doing something naughty, I changed that from version 11.2.0 > to 10.2.0-1. Same problem all the way. Running gcc from the terminal emulator > works (but then I don't get to use Emacs' M-x ` and the like). > I'm using 64-bit Windows 7 Pro [blush]. Is it still supposed to work on that? > I don't seem to have a problem with a laptop running Windows 10. > `uname -r` returns 3.3.4(0.341/5/3). > I've spent a few hours looking at the mailing list archives (probably > incompetently) and Googling, without success. Perhaps this is the same issue with: https://cygwin.com/pipermail/cygwin/2022-March/251162.html which is already fixed in cygwin git head. https://cygwin.com/pipermail/cygwin-patches/2022q1/011865.html -- 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
Emacs crashing after M-x compile after Cygwin updates
Hi, all. I've been happily compiling simple C programs under Emacs (emacs-w32) under Cygwin. Yesterday I wanted to install libedit-dev. While I was doing that, setup...exe marked a few dozen other packages for upgrades. I didn't notice which. Now, if I `emacs hello.c` and M-x compile gcc -o hello hello.c the compilation works... but then, a few seconds later, Emacs SEGVs. emacs-nox does the same but without the delay. I've tried Emacs versions 27.2-1, 28.0.60-1.f7e6c199bf, and 27.1. Then, in case it was gcc doing something naughty, I changed that from version 11.2.0 to 10.2.0-1. Same problem all the way. Running gcc from the terminal emulator works (but then I don't get to use Emacs' M-x ` and the like). I'm using 64-bit Windows 7 Pro [blush]. Is it still supposed to work on that? I don't seem to have a problem with a laptop running Windows 10. `uname -r` returns 3.3.4(0.341/5/3). I've spent a few hours looking at the mailing list archives (probably incompetently) and Googling, without success. -- 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: OpenSSH 8.9p1-1 Connects successfully but then hangs - Killing ssh-agent resolves the issue
Greetings, Jim Garrison via Cygwin!
Replying to the first post to reduce quoting, but I did read the entire thread.
> My Cygwin ssh client stopped working... It would successfully connect to
> the remote (Debian) host but then hang without displaying the command
> prompt. See debug output attached, as well as cygcheck output.
> I decided to run setup to see if there was a newer version of openssh.
> In preparation for that I always terminate all Cygwin processes because
> they will interfere with the update. I killed the ssh-agent process and
> on a whim decided to try connecting again. This time it worked.
> This would seem to indicate something in ssh-agent is interfering with
> the connection. There are no credentials loaded into ssh-agent.
I've encountered similar issue with ssh-pageant myself.
The explanation (as I see it) is this:
At certain point in its lifetime, the agent gets stuck and cease
to respond to the requests.
SSH attempting to contact the hung agent, the connection thread responds but
internal storage is somehow locked and never return any usable info on which
the client could meaningfully act. Since neither agent, nor SSH have any
guarding code against slow responses in this place, entire system hangs
indefinitely.
This is how the problem is observed. The following is a pure guesswork (with a
workaround).
I'm only exclusively observing this issue on my notebook. My guess is when it
awakes from hibernation, some internal state is not managed well. The delay in
agent response gets increasingly larger until it reaches the point of
intolerability. I've made a workaround like the following:
_check_agent() {
test -f "$HOME/.ssh/agent" && . "$HOME/.ssh/agent" > /dev/null
ssh-add -l > /dev/null 2>&1 &
sleep 1
if kill -0 $! 2> /dev/null; then
echo "$( basename "$0" ): ssh-add: the agent is hung, unable to continue"
>&2
exit 1
fi
if ! wait $!; then
echo "$( basename "$0" ): ssh-add: no identities or unable to contact the
agent" >&2
exit 2
fi
}
What it does is:
1. Run a command to list available keys, detached.
2. Wait a second to let the command complete, if all goes well.
3. Test if a listing command is still around. If it does, assume hung agent
and report an error.
4. Also report an error if no keys are registered with agent or agent is dead.
--
With best regards,
Andrey Repin
Monday, April 4, 2022 9:16:49
Sorry for my terrible english...
--
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: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Greetings, James! > Never mind I'd say. I got the error when launching > C:\Appz\Cygwin\Cygwin.bat > Which is just > @echo off > C: > chdir C:\Appz\Cygwin\bin > bash --login -i > If however I run > C:\cygwin64\bin\mintty.exe > It works fine. This means you have two different Cygwin versions installed. If you never use the other one, I strongly suggest removing it, as an unused and unmaintained program is often a good target for various troublemakers. And that other version of Cygwin you have IS unmaintained, judging by the error you receive from it (which was fixed over a decade ago). > On Sat, Apr 2, 2022 at 8:28 AM James wrote: >> Hi there, >> >> >> I just got that error message, asking me to report it here. >> >> 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute >> FAST_CWD pointer. Please report this problem to the public mailing list >> cygwin@cygwin.com >> >> Not sure if it's interesting? -- With best regards, Andrey Repin Monday, April 4, 2022 10:26:57 Sorry for my terrible english... -- 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
