Classic running out of memory... huh? what? <long>

[Kevin D. Clark]

bruce.labitt at autoliv.com writes:

> Anyways, the program seems to run out of memory after processing many 
> blocks.  So either there is a memory leak, or something else going on. 
> 
> Any suggestions?
...
> Any good memory tracking tools?  I have used valgrind but not gained much 
> insight.  Must be operator error...

I would suggest that you run your program in conjunction with Valgrind
with some small-to-medium sized datasets and fix the problems that are
reported.  I say "small-to-medium sized" so that you don't have to
wait a long time to see what is going wrong.

I am a huge fan of Valgrind.  It is an awesome tool that is worth
knowing how to use.

Regards,

--kevin
-- 
GnuPG ID: B280F24E                God, I loved that Pontiac.
alumni.unh.edu!kdc                -- Tom Waits
http://kdc-blog.blogspot.com/