On Tue, 2 Oct 2001, Christoph Reichenbach wrote: > As it looks now, I can't reproduce it, and our tools are worthless (except > for making malloc()/free() more sensitive towards heap corruption), so > this has to be debugged manually.
Okay, I manually inserted "free(s); exit(0);" at various places and narrowed things down: When free'ing gamestate in main.c before game_run() is called, everything is fine. When free'ing the pointer (s, or _s) in the beginning of game_run(), the heap/pointer is corrupted. Nothing jumps out at me (or my boyfriend who's sitting next to me) as being wrong in the code. I tried removing the 'static' modifier in a few places, but that didn't change the behaviour. What's the next step? -- http://www.clock.org/~matt
