Re: Is this a bug?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Is this a bug?
Date	2020-08-18 18:27 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.283.1597789691.2469.bug-bash@gnu.org> (permalink)
References	<1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu> <1312274972.4025864.1597785278610@mail.yahoo.com> <6575997b-0217-046a-8ef1-0437571475ca@case.edu>

Show all headers | View raw

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/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Is this a bug? Chet Ramey <chet.ramey@case.edu> - 2020-08-18 18:27 -0400

csiph-web