I've got RHEL3 and I'm running valgrind 3.1.1 - seems to be working OK
now, and its really not too bad. I think I'm homing in on it, though
any hints for making it easier are welcome!
Right now it looks like I'm calling job_null with a bad smcb - things
are a little weird ...
Usually, when we start a new SM we immediately begin executing it until
it blocks, then we return to what we were doing. The test I'm running
is weird because the little SM I'm running concurrently in the middle of
a get_config doesn't DO anything, so it never blocks, so it actually
runs to completion before returning to the caller.
Now, I considered altering this so that the new SMs are NOT started
immediately, but scheduled to run, but after talking to Pete decided not
to do that - after all, REAL SMs will block, and this might reduce latency.
So, what I'm getting it is, I might be calling job_null on a SM that
later completes and gets freed. I'm not sure, I'm trying to figure that
out and decide on a way to cleanly deal with that.
(you may recall I said back in July that termination was the real
bug-a-boo to this thing)
Walt
Rob Ross wrote:
hey walt,
i've had mixed results. what os and distro are you trying?
rob
Walter B. Ligon III wrote:
has anyone run the server with valgrind?
I have a nasty memory bug and I'm trying to use it to find the
problem, but the server won't run with it - tells me some of the db
functions don't work????
Any experience?
Walt
--
Dr. Walter B. Ligon III
Associate Professor
ECE Department
Clemson University
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
