Paul, Run "top -d 1" from another terminial before starting your program. It should show clearly the memory usage climbing if your code has a leak. Hit shift-M to sort by memory usage.
If this is indeed the case I suggest that you recompile with "-g" and then run your program under "valgrind" to find the source of your memory leak. Luck, -Brett. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
