Hi. No matter what I try, valgrind on 7.3-STABLE is giving me this, both Valgrind ports: valgrind: Startup or configuration error: Can't establish current working directory at startup valgrind: Unable to start up properly. Giving up. What do I need to do to make it work? -- VZ
On 06/10/2011, at 7:36, V?clav Zeman wrote:> No matter what I try, valgrind on 7.3-STABLE is giving me this, both Valgrind > ports: > > valgrind: Startup or configuration error: > Can't establish current working directory at startup > valgrind: Unable to start up properly. Giving up. > > What do I need to do to make it work?It might need proofs mounted, not sure though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
On Wed, Oct 05, 2011 at 11:06:04PM +0200, V??clav Zeman wrote:> Hi. > > No matter what I try, valgrind on 7.3-STABLE is giving me this, both Valgrind > ports: > > valgrind: Startup or configuration error: > Can't establish current working directory at startup > valgrind: Unable to start up properly. Giving up. > > What do I need to do to make it work?I just tried it on 7.4 and it appeared to work for me. Your error message suggests a permissions problem. If you ran pwd from your shell in the directory you were trying to run valgrind from and as the user you were trying to run valgrind from, does pwd give an error also? Gary
On Wed, 05 Oct 2011 23:06:04 +0200 =?UTF-8?B?VsOhY2xhdiBaZW1hbg==?= <v.haisman@sh.cvut.cz> wrote:> Hi. > > No matter what I try, valgrind on 7.3-STABLE is giving me this, both Valgrind > ports: > > valgrind: Startup or configuration error: > Can't establish current working directory at startup > valgrind: Unable to start up properly. Giving up. > > What do I need to do to make it work?Try running valgrind under ktrace (& view with kdump). That will tell you what directory it is trying to access or what syscall fails and why.