Re: [Valgrind-users] Working directory

[Dallman, J. <joh...@si...>]

> I've got a program which seems to cause heap corruption so I thought valgrind would be
> able to tell me where this occurs. The trouble is the program uses data files from the
> running directory for configuration purposes and running the program under valgrind
> seems to prevent it finding these data files. I therefore cannot reproduce the
> conditions which cause the problem.

How are you launching your program? The way I do it is to set up a working directory with
the files I need in it, and run the program without Valgrind to verify that it's all set up.

For example, I have kid.out as the executable. with lipsini.lsp as its startup commands.

        ls shows me:
        kid.out lispini.lsp
        kid.out runs it.

Then I just run

        /usr/local/bin/valgrind kid.out

and that runs kid.out under Valgrind with the directory I was in as the current directory.

--
John Dallman


-----------------
Siemens Industry Software Limited is a limited company registered in England and Wales.
Registered number: 3476850.
Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD.