Re: Exasperating memory corruption

[Marcus G. Daniels]

>>>>> "WS" == William S Shu <address@hidden> writes:

WS> - what can so corrupt memory that it
WS> affects access to locations and local variables?  It is easier to
WS> understand corruption of data values, not memory location
WS> (addresses) to parameters and local variables.

Don't compile with optimization -- the compiler may rearrange things
on you, and it will appear that changes happen across multiple lines
of code when you're looking at it with GDB.

And like Paul says, you should take care to return the right thing (or self)
from all methods.  That's a common source of crashes.   But I don't see
examples of where that might be a problem, but you only posted parts
of your program.

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.