Re: [Valgrind-users] Valgrid 2.1.2

[Tom H. <th...@cy...>]

In message <410...@pe...>
          Andrew Hodgetts <and...@pe...> wrote:

> I have just upgraded valgrind and have found that if I run
> 
> valgrind --tool=memcheck -v ls
> 
> it works fine, but if I run
> 
> valgrind --tool=memcheck -v ls val*
> 
> I get a core dump straight away.
> 
> Is this a bug, or am I doing something stupid?

A core dump in what? ls? or valgrind?

Valgrind is usually fairly verbose about failures so does it manage
to print anything or does it literally just stop with a core dump and
no output?

What does val* expand to in the directory in question? What happens
if you try this in another directory with less files that match that
pattern?

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/