Re: valgrind on FreeBSD?
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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0) 78028 memcheck-amd64-free RET mmap 17179906048/0x49000 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: valgrind on FreeBSD?
On Sun, Oct 09, 2011 at 03:25:23PM +0200, V??clav Zeman wrote:
> 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0)
> 78028 memcheck-amd64-free RET mmap 17179906048/0x49000
> 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"?
I can't reproduce this problem on our RELENG_7 system (7.4-STABLE,
though i386). Filesystem being accessed by valgrind is UFS2 + SU.
$ valgrind /usr/local/bin/mysql
==47587== Memcheck, a memory error detector
==47587== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==47587== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==47587== Command: /usr/local/bin/mysql
==47587==
Welcome to the MySQL monitor. Commands end with ; or \g.
{snip}
And this is what I see under "ktrace valgrind /usr/local/bin/mysql":
47590 memcheck-x86-freebs RET execve 0
47590 memcheck-x86-freebs CALL getpid
47590 memcheck-x86-freebs RET getpid 47590/0xb9e6
47590 memcheck-x86-freebs CALL
__sysctl(0x3955b604,0x4,0x38473200,0x3955b62c,0,0)
47590 memcheck-x86-freebs SCTL "kern.proc.vmmap.47590"
47590 memcheck-x86-freebs RET __sysctl 0
47590 memcheck-x86-freebs CALL
mmap(0x5fe08000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0
,0)
47590 memcheck-x86-freebs RET mmap 1608548352/0x5fe08000
47590 memcheck-x86-freebs CALL getrlimit(RLIMIT_DATA,0x3984cf30)
47590 memcheck-x86-freebs RET getrlimit 0
47590 memcheck-x86-freebs CALL setrlimit(RLIMIT_DATA,0x3955bb98)
47590 memcheck-x86-freebs RET setrlimit 0
47590 memcheck-x86-freebs CALL getrlimit(RLIMIT_STACK,0x3984cf40)
47590 memcheck-x86-freebs RET getrlimit 0
47590 memcheck-x86-freebs CALL
__sysctl(0x3955b62c,0x2,0x3955b604,0x3955b634,0x3818cab2,0x12)
47590 memcheck-x86-freebs SCTL "sysctl.name2oid"
47590 memcheck-x86-freebs RET __sysctl 0
47590 memcheck-x86-freebs CALL
__sysctl(0x3955b604,0x2,0x3955b678,0x3955b674,0,0)
47590 memcheck-x86-freebs SCTL "hw.instruction_sse"
47590 memcheck-x86-freebs RET __sysctl 0
47590 memcheck-x86-freebs CALL __getcwd(0x38316fa0,0x3ff)
47590 memcheck-x86-freebs NAMI "/home/jdc"
47590 memcheck-x86-freebs RET __getcwd 0
47590 memcheck-x86-freebs CALL open(0x3955add0,O_RDONLY,0x100)
47590 memcheck-x86-freebs NAMI "/home/jdc/.valgrindrc"
47590 memcheck-x86-freebs RET open -1 errno 2 No such file or directory
47590 memcheck-x86-freebs
Re: valgrind on FreeBSD?
Václav Zeman wrote, On 9.10.2011 15:25: > 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0) > 78028 memcheck-amd64-free RET mmap 17179906048/0x49000 > 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"? > It is the nullfs! I have /home mounted using nullfs to /usr/home: /usr/home /home nullfs rw,multilabel,acls 0 0 When I run valgrind from the /usr based directory, it works: shell::wilx:/usr/home/users/wilx/tmp/yttool> valgrind --tool=memcheck ./yttool ==34679== Memcheck, a memory error detector ==34679== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==34679== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==34679== Command: ./yttool ==34679== ==34679== ==34679== HEAP SUMMARY: ==34679== in use at exit: 20,395 bytes in 119 blocks ==34679== total heap usage: 6,719 allocs, 6,600 frees, 716,787 bytes allocated ==34679== ==34679== LEAK SUMMARY: ==34679==definitely lost: 0 bytes in 0 blocks ==34679==indirectly lost: 0 bytes in 0 blocks ==34679== possibly lost: 134 bytes in 4 blocks ==34679==still reachable: 20,261 bytes in 115 blocks ==34679== suppressed: 0 bytes in 0 blocks ==34679== Rerun with --leak-check=full to see details of leaked memory ==34679== ==34679== For counts of detected and suppressed errors, rerun with: -v ==34679== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) But when I run it from the nullfs mount, it fails: shell::wilx:/usr/home/users/wilx/tmp/yttool> cd $HOME/tmp/yttool shell::wilx:~/tmp/yttool> valgrind --tool=memcheck ./yttool valgrind: Startup or configuration error: valgrind:Can't establish current working directory at startup valgrind: Unable to start up properly. Giving up. -- VZ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: valgrind on FreeBSD?
Jeremy Chadwick wrote, On 9.10.2011 15:46:
> On Sun, Oct 09, 2011 at 03:25:23PM +0200, V??clav Zeman wrote:
>> 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0)
>> 78028 memcheck-amd64-free RET mmap 17179906048/0x49000
>> 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"?
>
> I can't reproduce this problem on our RELENG_7 system (7.4-STABLE,
> though i386). Filesystem being accessed by valgrind is UFS2 + SU.
>
> $ valgrind /usr/local/bin/mysql
> ==47587== Memcheck, a memory error detector
> ==47587== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
> ==47587== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
> ==47587== Command: /usr/local/bin/mysql
> ==47587==
> Welcome to the MySQL monitor. Commands end with ; or \g.
> {snip}
>
> And this is what I see under "ktrace valgrind /usr/local/bin/mysql":
>
> 47590 memcheck-x86-freebs RET execve 0
> 47590 memcheck-x86-freebs CALL getpid
> 47590 memcheck-x86-freebs RET getpid 47590/0xb9e6
> 47590 memcheck-x86-freebs CALL
> __sysctl(0x3955b604,0x4,0x38473200,0x3955b62c,0,0)
> 47590 memcheck-x86-freebs SCTL "kern.proc.vmmap.47590"
> 47590 memcheck-x86-freebs RET __sysctl 0
> 47590 memcheck-x86-freebs CALL
> mmap(0x5fe08000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0
> ,0)
> 47590 memcheck-x86-freebs RET mmap 1608548352/0x5fe08000
> 47590 memcheck-x86-freebs CALL getrlimit(RLIMIT_DATA,0x3984cf30)
> 47590 memcheck-x86-freebs RET getrlimit 0
> 47590 memcheck-x86-freebs CALL setrlimit(RLIMIT_DATA,0x3955bb98)
> 47590 memcheck-x86-freebs RET setrlimit 0
> 47590 memcheck-x86-freebs CALL getrlimit(RLIMIT_STACK,0x3984cf40)
> 47590 memcheck-x86-freebs RET getrlimit 0
> 47590 memcheck-x86-freebs CALL
> __sysctl(0x3955b62c,0x2,0x3955b604,0x3955b634,0x3818cab2,0x12)
> 47590 memcheck-x86-freebs SCTL "sysctl.name2oid"
> 47590 memcheck-x86-freebs RET __sysctl 0
> 47590 memcheck-x86-freebs CALL
> __sysctl(0x3955b604,0x2,0x3955b678,0x3955b674,0,0)
> 47590 memcheck-x86-freebs SCTL "hw.instruction_sse"
> 47590 memcheck-x86-freebs RET __sysctl 0
> 47590 memcheck-x86-freebs CALL __getcwd(0x38316fa0,0x3ff)
> 47590 memcheck-x86-freebs NAMI "/home/jdc"
> 47590 memcheck-x86-freebs RET __getcwd 0
> 47590 memcheck-x86-freebs CALL open(0x3955add
Re: valgrind on FreeBSD?
On Sun, Oct 09, 2011 at 03:48:57PM +0200, V??clav Zeman wrote: > V??clav Zeman wrote, On 9.10.2011 15:25: > > 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0) > > 78028 memcheck-amd64-free RET mmap 17179906048/0x49000 > > 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"? > > > It is the nullfs! > > I have /home mounted using nullfs to /usr/home: > > /usr/home /home nullfs rw,multilabel,acls >0 0 > > When I run valgrind from the /usr based directory, it works: > > shell::wilx:/usr/home/users/wilx/tmp/yttool> valgrind --tool=memcheck ./yttool > ==34679== Memcheck, a memory error detector > ==34679== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > ==34679== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info > ==34679== Command: ./yttool > ==34679== > ==34679== > ==34679== HEAP SUMMARY: > ==34679== in use at exit: 20,395 bytes in 119 blocks > ==34679== total heap usage: 6,719 allocs, 6,600 frees, 716,787 bytes > allocated > ==34679== > ==34679== LEAK SUMMARY: > ==34679==definitely lost: 0 bytes in 0 blocks > ==34679==indirectly lost: 0 bytes in 0 blocks > ==34679== possibly lost: 134 bytes in 4 blocks > ==34679==still reachable: 20,261 bytes in 115 blocks > ==34679== suppressed: 0 bytes in 0 blocks > ==34679== Rerun with --leak-check=full to see details of leaked memory > ==34679== > ==34679== For counts of detected and suppressed errors, rerun with: -v > ==34679== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > > But when I run it from the nullfs mount, it fails: > > shell::wilx:/usr/home/users/wilx/tmp/yttool> cd $HOME/tmp/yttool > shell::wilx:~/tmp/yttool> valgrind --tool=memcheck ./yttool > valgrind: Startup or configuration error: > valgrind:Can't establish current working directory at startup > valgrind: Unable to start up properly. Giving up. Amazing how userland utilities behave differently depending upon the underlying filesystem type, eh? Good thing I asked what your underlying filesystem types were. Don't ever think that "it'll all just work". :-) I believe there are other issues/stipulations with nullfs (some have been reported over the years), so I'm not too surprised by this issue. I have
Re: valgrind on FreeBSD?
Jeremy Chadwick wrote, On 9.10.2011 16:11: > On Sun, Oct 09, 2011 at 03:48:57PM +0200, V??clav Zeman wrote: >> V??clav Zeman wrote, On 9.10.2011 15:25: >>> 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0) >>> 78028 memcheck-amd64-free RET mmap 17179906048/0x49000 >>> 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"? >>> >> It is the nullfs! >> >> I have /home mounted using nullfs to /usr/home: >> >> /usr/home /home nullfs rw,multilabel,acls >>0 0 >> >> When I run valgrind from the /usr based directory, it works: >> >> shell::wilx:/usr/home/users/wilx/tmp/yttool> valgrind --tool=memcheck >> ./yttool >> ==34679== Memcheck, a memory error detector >> ==34679== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. >> ==34679== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info >> ==34679== Command: ./yttool >> ==34679== >> ==34679== >> ==34679== HEAP SUMMARY: >> ==34679== in use at exit: 20,395 bytes in 119 blocks >> ==34679== total heap usage: 6,719 allocs, 6,600 frees, 716,787 bytes >> allocated >> ==34679== >> ==34679== LEAK SUMMARY: >> ==34679==definitely lost: 0 bytes in 0 blocks >> ==34679==indirectly lost: 0 bytes in 0 blocks >> ==34679== possibly lost: 134 bytes in 4 blocks >> ==34679==still reachable: 20,261 bytes in 115 blocks >> ==34679== suppressed: 0 bytes in 0 blocks >> ==34679== Rerun with --leak-check=full to see details of leaked memory >> ==34679== >> ==34679== For counts of detected and suppressed errors, rerun with: -v >> ==34679== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) >> >> But when I run it from the nullfs mount, it fails: >> >> shell::wilx:/usr/home/users/wilx/tmp/yttool> cd $HOME/tmp/yttool >> shell::wilx:~/tmp/yttool> valgrind --tool=memcheck ./yttool >> valgrind: Startup or configuration error: >> valgrind:Can't establish current working directory at startup >> valgrind: Unable to start up properly. Giving up. > > Amazing how userland utilities behave differently depending upon the > underlying filesystem type, eh? Good thing I asked what your underlying > filesystem types were. Don't ever think that "it'll all just work". > :-) > > I believe there are other issues/stipulations with nul
Re: valgrind on FreeBSD?
On Sun, Oct 09, 2011 at 04:18:48PM +0200, V??clav Zeman wrote: > Jeremy Chadwick wrote, On 9.10.2011 16:11: > > On Sun, Oct 09, 2011 at 03:48:57PM +0200, V??clav Zeman wrote: > >> V??clav Zeman wrote, On 9.10.2011 15:25: > >>> 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(0x49000,0x40,PROT_READ|PROT_WRITE|PROT_EXEC,MAP_PRIVATE|MAP_FIXED|MAP_ANON,0x,0) > >>> 78028 memcheck-amd64-free RET mmap 17179906048/0x49000 > >>> 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"? > >>> > >> It is the nullfs! > >> > >> I have /home mounted using nullfs to /usr/home: > >> > >> /usr/home /home nullfs rw,multilabel,acls > >>0 0 > >> > >> When I run valgrind from the /usr based directory, it works: > >> > >> shell::wilx:/usr/home/users/wilx/tmp/yttool> valgrind --tool=memcheck > >> ./yttool > >> ==34679== Memcheck, a memory error detector > >> ==34679== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > >> ==34679== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info > >> ==34679== Command: ./yttool > >> ==34679== > >> ==34679== > >> ==34679== HEAP SUMMARY: > >> ==34679== in use at exit: 20,395 bytes in 119 blocks > >> ==34679== total heap usage: 6,719 allocs, 6,600 frees, 716,787 bytes > >> allocated > >> ==34679== > >> ==34679== LEAK SUMMARY: > >> ==34679==definitely lost: 0 bytes in 0 blocks > >> ==34679==indirectly lost: 0 bytes in 0 blocks > >> ==34679== possibly lost: 134 bytes in 4 blocks > >> ==34679==still reachable: 20,261 bytes in 115 blocks > >> ==34679== suppressed: 0 bytes in 0 blocks > >> ==34679== Rerun with --leak-check=full to see details of leaked memory > >> ==34679== > >> ==34679== For counts of detected and suppressed errors, rerun with: -v > >> ==34679== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > >> > >> But when I run it from the nullfs mount, it fails: > >> > >> shell::wilx:/usr/home/users/wilx/tmp/yttool> cd $HOME/tmp/yttool > >> shell::wilx:~/tmp/yttool> valgrind --tool=memcheck ./yttool > >> valgrind: Startup or configuration error: > >> valgrind:Can't establish current working directory at startup > >> valgrind: Unable to start up properly. Giving up. >
rsync corrupted MAC
Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] The script: #!/bin/sh /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/etc/ \ /vault/backup/TBH/etc/ /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/home/ \ /vault/backup/TBH/home/ #/usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/usr/local/pgsql/backups/ \ #/vault/backup/TBH/pgsql/ /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/var/named/ \ /vault/backup/TBH/named/ It seems to move and be at a random spot in the file. Then it will move to a different file. Ideas? Source is 8.2-STABLE, and the Destination/controller is 9.0-BETA3. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
bsdinstall partitioning
Hi, I just had my first encounter with the new installer. I chose manual partitioning, created a BSD disk (not GPT) with one swap and the rest for /. Rest of the installation went fine but then my system didn't boot. I repeated everything and I chose guided partitioning. This time it worked but I think the manual way with BSD disk format should also work as it did in sysinstall. Besides, the partition types (freebsd-ufs, freebsd-swap and freebsd-boot) should be listed somehow or there should be radio buttons. If you choose manual partition with GPT, only the first two are shown in the description so one may not know that there is also a freebsd-boot type, which is mandatory. Anyway, the rest of the installer and the configuration is very convenient and I loved that I could configure my wifi connection w/o hand-editing the config files, so thanks a lot to Nathan for the hard work! Cheers, Gabor ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
