Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > gnu.bash.bug > #16779
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Is this a bug? |
| Date | 2020-08-19 14:44 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.400.1597862681.2469.bug-bash@gnu.org> (permalink) |
| References | (4 earlier) <6575997b-0217-046a-8ef1-0437571475ca@case.edu> <1699062943.4171052.1597809756404@mail.yahoo.com> <16e6944b-9707-a80c-3602-e76edcca64ec@case.edu> <630008166.4463802.1597857290469@mail.yahoo.com> <054462f1-e801-bdcc-8f0d-b880ef8eab79@case.edu> |
On 8/19/20 1:14 PM, George R Goffe wrote: > Chet, > > How can I help capture data about this problem? > > When I run bash in one konsole and it hangs, I do an strace on that pid and the strace -xvfp <pid> always shows pselect. Eventually, the results come back but til then, the session is frozen. You can try running gdb on bash from another terminal, attaching to the hanging bash process with `attach <pid>', and generating a backtrace from gdb. That would at least give you the call stack. Make sure to run the bash instance you're testing with `--noprofile --norc' to get as vanilla an environment as possible. -- ``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? Chet Ramey <chet.ramey@case.edu> - 2020-08-19 14:44 -0400
csiph-web