bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in bash 4.4-beta: suspending and restarting "man" program


From: Keith Thompson
Subject: Re: Bug in bash 4.4-beta: suspending and restarting "man" program
Date: Fri, 30 Oct 2015 20:25:29 -0700

Whatever the problem is, it seems to be subtle. I can't *reliably*
reproduce it on the original Debian 6 system.

I saw the problem in a shell that had been running for a couple of weeks,
with several thousand commands executed. Replacing the shell process with
"exec bash -l" (using the same version of bash) did not fix the problem,
but starting a new shell seems to have fixed it, at least for now.

For a while, I had two running login shells, one that had the problem
and one that didn't.  Comparing the output of "set" and "shopt" from
both shells didn't show any differences that could explain this.

My best guess at this point is that some internal data structure was
corrupted as a result of *something* that I did. I wish I could be more
specific. I'll keep an eye on it, and let you know if I can come up with
something more concrete.

Any suggestions on more data I can gather if this happens again?
I can try attaching strace and sending a copy of the log.

On Fri, Oct 30, 2015 at 2:31 PM, Keith Thompson <keithsthompson@gmail.com> wrote:
I just tried it on a two VMs running Debian 6 and 7, respectively.
The problem did not occur.

It also doesn't occur on the original Debian 6 system if I run it as "bash --norc".
(Sorry, I should have tried that in the first place.)

So the problem has something to do with my own setup scripts.
I'll investigate further and get back to you.

On Fri, Oct 30, 2015 at 3:55 AM, Chet Ramey <chet.ramey@case.edu> wrote:
On 10/28/15 10:02 PM, Keith Thompson wrote:
> I'm running bash 4.4-beta, built from bash-4.4-beta.tar.gz, on two
> different x86_64 systems, one running Debian 6.0.10 and another running
> Linux Mint 17.3.
>
> On both systems, if I run "man rm" (for example) I can read the "rm(1)"
> man page using "less" (my $MANPAGER is set to "less -s -r").  If I then
> type Ctrl-Z, the "man" and "pager" processes are suspended and the screen
> is restored its previous state.
>
> On the Debian system, I don't get a new shell prompt (this is the
> bug). The terminal continues to accept and echo input, but it's otherwise
> stuck.  Ctrl-C and Ctrl-Z are echoed as "^C" and "^Z", but are otherwise
> ignored.  I can recover by killing the "man" process from another window.

I don't have a Debian 6 system, but I can't reproduce this on Debian 7.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/



--



--
Keith Thompson <Keith.S.Thompson@gmail.com>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]