|
From: Tom H. <th...@cy...> - 2004-08-02 07:25:21
|
In message <410...@pe...>
Andrew Hodgetts <and...@pe...> wrote:
> 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)
That's exceptionally odd. I was kind of assuming that if it was
failing very early (which it obviously is) then it would be down
to the val* having expanded to a large number of argument that was
overflowing something but obviously not.
The problem is that lots of people are using 2.1.2 and not seeing
this so it must be something about your system that is upsetting
it at a guess. What distribution/kernel/glibc are you using?
Does it work with --tool=none by the way?
It's possible that running the while thing under strace might
reveal some sort of clue into what it happening.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|