|
From: Jason G. <jga...@la...> - 2003-08-19 13:55:42
|
> -----Orig > Let's see: > > [~/grind/annelid] gcc a.o memcheck/vgskin_memcheck.so > coregrind/valgrind.so [~/grind/annelid] > VG_ARGS=--suppressions=default.supp; a.out ==26034== > Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux. > ==26034== Copyright (C) 2002-2003, and GNU GPL'd, by Julian Seward. > ==26034== Using valgrind-20030725, a program supervision > framework for x86-linux. > ==26034== Copyright (C) 2000-2003, and GNU GPL'd, by Julian Seward. > ==26034== Estimated CPU clock rate is 1404 MHz ==26034== For > more details, rerun with: -v ==26034== ==26034== ==26034== > ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from > 0) ==26034== malloc/free: in use at exit: 0 bytes in 0 blocks. > ==26034== malloc/free: 0 allocs, 0 frees, 0 bytes allocated. > ==26034== For a detailed leak analysis, rerun with: > --leak-check=yes ==26034== For counts of detected errors, > rerun with: -v > > So the answer seems to be yes, with some provisos: > > - You have to link with a particular skin. I linked with Memcheck > above. > > - You have to put the skin .so before valgrind.so when linking. > > - You have to setup $VG_ARGS, by adding a --suppressions= > entry, at the > least. > > I'd be interested to know why you want to do this. That's very nice. Thank you. The reason I want to do this: I run a MUD. I know it has some invalid read/writes and more than likely some memory issues (judging from the cores I've been getting :) ) The problem is, that I cannot reasonable run the MUD in valgrind and find these problems. I need the players to get on there and do what players do (hours or DAYS before a crash occurs). Therefore, I was hoping I could just create a single executable for simplicity. I could run it through the executable, but I thought this would be a little nicer. Thanks! |