If someone would like to, also is it posssible to compile it to a rom, well I know its possible cause the original rom was compiled from it, wondering if anyone here would be able to do it
Whoa, hold the phone. Memory leaks are probably one of, if not the hardest error to find by debugging. It's not a runtime error so the compiler won't catch it. While a capable programmer "could" find the error, this is likely a very daunting task that could require hours and hours of work. It's hard enough to find memory leaks in your own code, let alone someone else's...
PS - And this is why a lot of people prefer Java to C++. Java allocates memory for you, C++ forces you to do it yourself. And if you aren't careful in C++, then you get errors like this!
Jonas - this is in C, not C++, so it's a little bit different (but not much).
I don't think that I could find something like that, but for something as simple as a game from that generation, on today's computers I would think you could monitor the workspace more thoroughly and see where things are blowing up. My guess would be that there is a poorly written recursion or iteration that keeps reallocating memory for internal variables and then doesn't clear what it used.
^ Yeah it's definitely either in a loop or some recursion function that gets called repeatedly. Still, tracking down memory leaks is not fun and is very tedious...
Comments
There are a number of us that could easily dig into the headers and C-files and see what's going on.
So...is that what you're asking somebody to do?
PS - And this is why a lot of people prefer Java to C++. Java allocates memory for you, C++ forces you to do it yourself. And if you aren't careful in C++, then you get errors like this!
I don't think that I could find something like that, but for something as simple as a game from that generation, on today's computers I would think you could monitor the workspace more thoroughly and see where things are blowing up. My guess would be that there is a poorly written recursion or iteration that keeps reallocating memory for internal variables and then doesn't clear what it used.