22 Jun
2002
22 Jun
'02
6:40 a.m.
Finally got it. In the end the problem wasn't in the list work at all. Way earlier in the program, I'd allocated memory for an array [1..x], then accessed it as [0..x]. On freeing the memory, I guess something funny was set up in the memory manager that came back to bite me way later. So... is there a compiler option I could have set that would have told me about this illegal memory access? well, now perhaps I can sleep. Toby
8820
Age (days ago)
8822
Last active (days ago)
8 comments
4 participants
participants (4)
-
CBFalconer -
Frank Heckenbach -
Maurice Lombardi -
Toby Ewing