Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SIGKILL



> I've gotten valgrind and installed it, and ran some simple tests (ie
> valgrind ls -l, etc) but when I go to run it against my application it
> comes
> to a standstill.  What is the normal degree of slowdown from this tool?
> It's been almost 10 minutes without moving.

I haven't actually used valgrind, but from what I've read, it runs your
program on a simulated CPU and intercepts every system call, so that it
can keep track of every byte of memory that gets allocated and how that
memory is used.  Since your application is dying because the OS runs out
of memory, it stands to reason that valgrind would slow it down a lot.

-- 
"Most organizations that are used to failure are unable to tolerate
success."
  --Scott Ambler
// seth gordon // sethg at ropine.com // http://ropine.com/sethg/cv.html //





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org