Yes, the problem still exists on Precise. Other issues I encounted:
`valgrind -- foo<TAB>` becomes `valgrind -- ` (empty). `valgrind -- <TAB><TAB>` shows `yes` or `no` as options. I expect a list of commands.
This applies recursively: `valgrind -- ls -- foo<TAB>` becomes `valgrind -- ls -- ` (empty).
Yes, the problem still exists on Precise. Other issues I encounted:
`valgrind -- foo<TAB>` becomes `valgrind -- ` (empty). `valgrind -- <TAB><TAB>` shows `yes` or `no` as options. I expect a list of commands.
This applies recursively:
`valgrind -- ls -- foo<TAB>` becomes `valgrind -- ls -- ` (empty).