On 2008/04/20 12:14, Matthias Klose [EMAIL PROTECTED] wrote:
tag 465979 + moreinfo
thanks
- please recheck with 3.2,
- is this reproducible with certain history content?
With 3.2, the bug is different - it does not hang anymore, it exits
instead.
Here is the stack trace with debugging
tag 465979 + moreinfo
thanks
- please recheck with 3.2,
- is this reproducible with certain history content?
Max Kellermann writes:
Package: bash
Version: 3.1dfsg-8
bash consumes 100% CPU, strace says:
read(0, , 1) = 0
read(0, , 1) =
Package: bash
Version: 3.1dfsg-8
bash consumes 100% CPU, strace says:
read(0, , 1) = 0
read(0, , 1) = 0
The stack trace lets me assume this is actually a bug in readline
(feel free to reassign this bug):
(gdb) bt
#0 0xb7f28410 in
3 matches
Mail list logo