[Top][All Lists]

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

Re: Is this a bug?

From: George R Goffe
Subject: Re: Is this a bug?
Date: Wed, 19 Aug 2020 04:02:36 +0000 (UTC)


I've been thinking about what you've said below... that bash is waiting for 
input. If this were the case, ctrl-c would return to the bash prompt 
immediately. Yes? What I'm seeing is that with a partial filename entered 
followed by the tab key is hit which results in nothing due to an 
uninterriputible sleep. Ctrl-c does not stop the filename completion process.

Does this make any sense?


On Tuesday, August 18, 2020, 3:28:01 PM PDT, Chet Ramey <chet.ramey@case.edu> 

On 8/18/20 5:14 PM, George R Goffe wrote:
> Chet,
> Please accept my apology for not responding to your email sooner.
> I have the bash source from the(?) repository. I followed Dimitris suggestion 
> and found bash hung in a system call named "pselect". I did a grep on the 
> source and found the only two ".c" files using "pselect":

If it's in pselect, it's waiting for input. It's probably not performing
completion at all. It may have read the directory, found no common prefix
for the files it found, `rang' the visible bell, and gone back to waiting
to read the next input character.

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

reply via email to

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