|
From: b h <bhh...@ma...> - 2003-09-12 15:56:44
|
This one doesn't for, tho I have other daemons that do that I'm trying to get working as well. I assume for those I just need to use the --track-children=yes flag, right? More info - appears to be chown and setuid problem. Is this known? This is on a SuSE SLES8 system. thx.bri. pdoslinux:~ # file p p: setgid ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped pdoslinux:~ # chown osseal:osseal p pdoslinux:~ # ls -l p -r-xr-sr-x 1 osseal osseal 61115 Sep 12 10:44 p* pdoslinux:~ # valgrind ./p AOSUT0407I Could not get the credential of the invoker: 0x35a6200e: AOSSS0014E PDOSD is not running (pd / oss) pdoslinux:~ # chown root:root p pdoslinux:~ # ls -l p -r-xr-sr-x 1 root root 61115 Sep 12 10:44 p* pdoslinux:~ # valgrind ./p ==24547== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. ==24547== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. ==24547== Using valgrind-20030725, a program supervision framework for x86-linux. ==24547== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. ==24547== Estimated CPU clock rate is 398 MHz ==24547== For more details, rerun with: -v ==24547== ==24547== Conditional jump or move depends on uninitialised value(s) ==24547== at 0x804945F: main (in /root/p) ==24547== by 0x403294A1: __libc_start_main (in /lib/libc.so.6) ==24547== by 0x8048CB0: (within /root/p) AOSUT0407I Could not get the credential of the invoker: 0x35a6200e: AOSSS0014E PDOSD is not running (pd / oss) ==24547== ==24547== ERROR SUMMARY: 8 errors from 8 contexts (suppressed: 5 from 2) ==24547== malloc/free: in use at exit: 14224 bytes in 73 blocks. ==24547== malloc/free: 188 allocs, 115 frees, 44197 bytes allocated. ==24547== For a detailed leak analysis, rerun with: --leak-check=yes ==24547== For counts of detected errors, rerun with: -v ----- Original Message ----- From: Steve G <lin...@ya...> Date: Thu, 11 Sep 2003 18:00:19 -0700 (PDT) To: Brian Horton <bhh...@ma...> Subject: Re: [Valgrind-users] no output > >Trying to use valgrind on a product I support and it's not > >working - I don't get any of the ==pid== output at all > > Does your program fork? Many daemons need to be modified not to > fork or a command line option has to be given to keep it in the > foreground or nothing comes out. > > -Steve Grubb > -- __________________________________________________________ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers |
|
From: Michael S. <ms...@xi...> - 2003-09-15 01:59:07
|
On Saturday 13 September 2003 01:54, b h wrote: > This one doesn't for, tho I have other daemons that do that I'm trying to > get working as well. I assume for those I just need to use the > --track-children=yes flag, right? > > More info - appears to be chown and setuid problem. Is this known? Valgrind relies on LD_PRELOAD to load itself into the executable at runtime. The linker ignores LD_PRELOAD on setuid binaries (neccesary, otherwise any user could make a setuid application run whatever code they wanted - obviously a bad thing with things setuid root). So you can't use valgrind on this application as-is. You'll have to un-setuid it, then run it directly as the appropriate user. Mike |