🚀 go-pugleaf

After running purify (a program for helping detect memory leaks) over an
interviews program, it indicated that some already freed memory was being
read during a table iterator next call.  The code which causes this
problem looks as follows:

  for(TableIterator(TableMethodsImpl) i(*_table); i.more(); i.next())
    _table->remove(i.cur_key());

The memory is freed in Table(TableMethodsImpl)::remove and then
accessed very soon afterwards.  It occurs before anything else is freed.
It is accessed in TableIterator(TableMethodsImpl)::next.  The obvious
problem is deleting memory while using an iterator.  As I am not very
good at debugging problems like this,  I would appreciate some way to
solve this problem.  One way would be a properly written Table::clear
routine, rather than implmenting it myself.


--
+-----------------+-------------------------------+-------------------------+
| Bill Poitras    | Molecular Simulations Inc.    | Tel (408)522-9229       |
| (bill)          | Sunnyvale, CA USA             |                         | 
|                 | FAX (408)732-0831             | bill@msi.com            |
+-----------------+-------------------------------+-------------------------+