Maybe doesn't apply here, but I've troubleshooted
problems with similar behavior before. For me, 9 out
of 10 times it has been a boundry check problem... ie.
pointer in an array stomps on memory before or after
memory allocation.
Rob
--- Paul M Foster <paulf@quillandmouse.com> wrote:
> I've got a C program I'm writing, in which something
> appears to be
> stepping on something else's memory. Does anyone
> have _personal_
> experience with a good memory checker/malloc
> replacement that might
> assist in debugging what's gone errant?
>
> Paul
>
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:14:25 EDT