From owner-freebsd-stable@FreeBSD.ORG Sun Oct 9 13:25:35 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF224106564A for ; Sun, 9 Oct 2011 13:25:34 +0000 (UTC) (envelope-from v.haisman@sh.cvut.cz) Received: from service1.sh.cvut.cz (service1.sh.cvut.cz [IPv6:2001:718:2::214]) by mx1.freebsd.org (Postfix) with ESMTP id 4565C8FC0A for ; Sun, 9 Oct 2011 13:25:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by service1.sh.cvut.cz (Postfix) with ESMTP id 82BEC1242E2; Sun, 9 Oct 2011 15:25:33 +0200 (CEST) X-Spam-Score: -100.484 X-Spam-Level: X-Spam-Status: No, score=-100.484 tagged_above=-255 required=5 tests=[ALL_TRUSTED=-1.44, AWL=0.530, CRM114_HAM_00=, RATWARE_GECKO_BUILD=1.426, SMTPAUTH_SHDOMAIN=-100] Received: from service1.sh.cvut.cz ([127.0.0.1]) by localhost (service1.sh.cvut.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBBUXEuveanq; Sun, 9 Oct 2011 15:25:26 +0200 (CEST) Received: from [10.0.0.1] (242.91.broadband5.iol.cz [88.100.91.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: v.haisman@sh.cvut.cz) by service1.sh.cvut.cz (Postfix) with ESMTP id F3343124295; Sun, 9 Oct 2011 15:25:25 +0200 (CEST) Message-ID: <4E91A0C3.7030305@sh.cvut.cz> Date: Sun, 09 Oct 2011 15:25:23 +0200 From: =?UTF-8?B?VsOhY2xhdiBaZW1hbg==?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4E8CC6BC.9040605@sh.cvut.cz> <20111006064038.CFB34B852@mail.bitblocks.com> In-Reply-To: <20111006064038.CFB34B852@mail.bitblocks.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: valgrind on FreeBSD? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2011 13:25:35 -0000 Bakul Shah wrote, On 6.10.2011 8:40: > On Wed, 05 Oct 2011 23:06:04 +0200 =?UTF-8?B?VsOhY2xhdiBaZW1hbg==?= 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. Hi. So I have done that and more. I have first updated from 7.3 to 8.2 (RELENG_8 actually). I have not managed to recompile all of the installed Ports yet, but I made sure to recompile valgrind and its dependencies. The same thing has happened! As I have said, I have done the ktrace and here is the interesting bit: 78028 valgrind NAMI "/usr/local/lib/valgrind/memcheck-amd64-freebsd" 78028 memcheck-amd64-free RET execve 0 78028 memcheck-amd64-free CALL getpid 78028 memcheck-amd64-free RET getpid 78028/0x130cc 78028 memcheck-amd64-free CALL __sysctl(0x39a91450,0x4,0x389a3800,0x39a91468,0,0) 78028 memcheck-amd64-free SCTL "kern.proc.vmmap.78028" 78028 memcheck-amd64-free RET __sysctl 0 78028 memcheck-amd64-free CALL mmap(0x400009000,0x400000,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0xffffffffffffffff,0) 78028 memcheck-amd64-free RET mmap 17179906048/0x400009000 78028 memcheck-amd64-free CALL getrlimit(RLIMIT_DATA,0x39e6a780) 78028 memcheck-amd64-free RET getrlimit 0 78028 memcheck-amd64-free CALL setrlimit(RLIMIT_DATA,0x39a919e0) 78028 memcheck-amd64-free RET setrlimit 0 78028 memcheck-amd64-free CALL getrlimit(RLIMIT_STACK,0x39e6a790) 78028 memcheck-amd64-free RET getrlimit 0 78028 memcheck-amd64-free CALL __getcwd(0x3882d700,0x3ff) 78028 memcheck-amd64-free NAMI ".." 78028 memcheck-amd64-free RET __getcwd -1 errno 2 No such file or directory 78028 memcheck-amd64-free CALL write(0x2,0x3830b060,0x6c) 78028 memcheck-amd64-free GIO fd 2 wrote 108 bytes "valgrind: Startup or configuration error: valgrind: Can't establish current working directory at startup " 78028 memcheck-amd64-free RET write 108/0x6c 78028 memcheck-amd64-free CALL write(0x2,0x3830b060,0x33) 78028 memcheck-amd64-free GIO fd 2 wrote 51 bytes "valgrind: Unable to start up properly. Giving up. " 78028 memcheck-amd64-free RET write 51/0x33 78028 memcheck-amd64-free CALL exit(0x1) Now what? Why would the __getcwd call be failing with "No such file or directory"? -- VZ