Using both 4.2 and 4.3, I can reproduce a segfault on completion (though
not using gdb)
This can happen very consistently using a time-consuming completion like
the one for `man`, eg:
$ man g^C
Attached is the trace from a core-file using `man gpg-agent g^C`
with bash 4.3.
Side note: as more a
On 4/14/13 7:08 PM, Raphaël Droz wrote:
> Using both 4.2 and 4.3, I can reproduce a segfault on completion (though
> not using gdb)
Thanks for the report. I will look at this for bash-4.3.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita bre
On 04/15/2013 01:08 AM, Raphaël Droz wrote:
Using both 4.2 and 4.3, I can reproduce a segfault on completion (though
not using gdb)
This can happen very consistently using a time-consuming completion like
the one for `man`, eg:
$ man g^C
Attached is the trace from a core-file using `man gpg-ag
On 4/13/13 1:35 AM, Ilya Basin wrote:
> Hi!
> I've got strange behavior. Here's my script:
>
> #!/bin/bash
> {
> trap '
> echo "in trap EXIT">&2
> ' EXIT
> sleep 4 &
> echo 'sleep 2'>&2
> sleep 2
> echo 'wait $!'>&2
> wait
