Ubuntu
valgrind package

  1. Vivid (15.04)
  2. Bug #840467
  3. Comment #4

Comment 4 for bug 840467

Revision history for this message
Peter Wu (lekensteyn) wrote :

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).