|
From: Andrew H. <and...@pe...> - 2004-08-02 06:44:28
|
Tom Hughes wrote: >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 > > > I only used 'ls' as an example. It occurs whenever I provide an argument for the program that I am trying to debug. Valgrind does not output anything and the core appears to be from valgrind. Below is the output straight from the console. /users/andrew/temp> ls * ata-raid-howto.pdf /users/andrew/temp> valgrind --tool=memcheck ls a* Segmentation fault (core dumped) |