TL;DR: Bug happened again, workaround works.
Have not tried dd yet, but whenever the bug happen I open a shell, use
bash Ctrl-R to find the one-liner below, press enter and expect that it
works around the bug.
for PROCESSLINE in $( grep -a ^script /proc/*/cmdline -l ) ; do cd
$(dirname
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a
# Confirmed that the workaround works in practice.
I had a hang, figured out which /usr/bin/script process was eating the
CPU, then issued:
head -n 1 /proc/7514/fd/4
and it continued working.
# Try to figure out what happens.
Below is after the problem was fixed (things worked well again, the
# Workaround? Tried once, works.
TL;DR: reading the slave pts from another process unfreezes and allows
continued operation
cd /proc/24621/fd
ls -al
total 0
dr-x-- 2 stephane stephane 0 avril 5 16:39 .
dr-xr-xr-x 9 stephane stephane 0 avril 5 15:13 ..
lrwx-- 1 stephane
# Reproducible? Tried once, takes about an hour.
This was enough to reproduce the bug once within about one hour :
open a terminal, type:
script
then on the shell prompt type:
yes
The 'yes' command produces as intended an infinite stream of lines with
the character 'y'.
After about one
## Status
Bug still occurs every few days, when I use Ubuntu 16.04, not when using
others.
## Trying to get more precise info
### Location in source code
Following https://wiki.ubuntu.com/DebuggingProgramCrash I could get an
interactive gdb prompt showing that it's blocked in the while loop
7 matches
Mail list logo
