Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16776
| From | George R Goffe <grgoffe@yahoo.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Is this a bug? |
| Date | 2020-08-19 04:02 +0000 |
| Message-ID | <mailman.291.1597809767.2469.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <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> <1699062943.4171052.1597809756404@mail.yahoo.com> |
Chet, 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? George... On Tuesday, August 18, 2020, 3:28:01 PM PDT, Chet Ramey <chet.ramey@case.edu> wrote: 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
Re: Is this a bug? George R Goffe <grgoffe@yahoo.com> - 2020-08-19 04:02 +0000
csiph-web