Date: Thu, 6 Oct 2011 16:24:39 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: =?iso-8859-1?Q?V=E1clav_Zeman?= <v.haisman@sh.cvut.cz> Cc: freebsd-stable List <freebsd-stable@freebsd.org> Subject: Re: valgrind on FreeBSD? Message-ID: <9658B13F-B8C3-4B48-9CF5-4AA3C7DFC217@gsoft.com.au> In-Reply-To: <4E8D368E.1030404@sh.cvut.cz> References: <4E8CC6BC.9040605@sh.cvut.cz> <40A58FC8-F369-40AE-A55A-EA0ABEFC5EA9@gsoft.com.au> <4E8D368E.1030404@sh.cvut.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/10/2011, at 15:33, V=E1clav Zeman wrote: > Daniel O'Connor wrote, On 6.10.2011 1:05: >>=20 >> On 06/10/2011, at 7:36, V=E1clav Zeman wrote: >>> No matter what I try, valgrind on 7.3-STABLE is giving me this, both = Valgrind >>> ports: >>>=20 >>> valgrind: Startup or configuration error: >>> Can't establish current working directory at startup >>> valgrind: Unable to start up properly. Giving up. >>>=20 >>> What do I need to do to make it work? >>=20 >> It might need proofs mounted, not sure though. > Did you mean "procfs"? Procfs is mounted: >=20 > procfs on /proc (procfs, local) OK, so much for that idea then :( > --=20 > VZ >=20 >=20 -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9658B13F-B8C3-4B48-9CF5-4AA3C7DFC217>