   Scripting - Strange Crash
  I've been adding a little scripting engine to a game I'm working on but have run into an odd error I can't seem to track down.  So far, the scripting system supports two commands, of the form: "CREATE SCENERY unique-id AT xcoord ycoord zlayer" and "QUIT".  I can seemingly use these two commands at will.  I am adding a third command "DESTROY SCENERY unique-id".  However, when I try to use this new command the application crashes sometimes reporting "This application has requested the Runtime to terminate it in an unusual way".  If I run the application through gdb, all it gives me are some indescript dll errors.  The application is written in C++ using OpenGL, OpenAL, STL, a couple BOOST libraries and is compiled with mingw through wxdev-c++.  Does anyone have any thoughts as to what might be the problem?  I will post any relevant code on request.  Thanks!   
  Are you able to destroy scenery from within the engine, without using scripts? Your problem may be in the destroy function, and not in the scripting interface at all.   ;  No, I am not able to destroy objects in-engine either... which is strange because it used to work.   ;  There's your problem :)   ;  I'm not certain, I'll dig around some more and post an update later today.  There seems to be something odd going on.   ;  Code would help.   ;  Just gave it another try (for the heck of it) and now the scripting command is working... I have not so much as recompiled since my last attempt.  It seems it responds differently either at different times of day or maybe its after reboots.   ;  Rebuilt, without changing any code, and now it breaks again giving the unusual termination error.  This is really weird.[EDIT] It works fine if I run it in windows xp compatability mode (I'm running windows 7 professional x64).  Anyone know what might cause this silly behavior?   ;  Added four more commands to the scripting engine, and all is well so long as the program is run in xp compatibility mode.  Wheeeeee   ;  You probably have some sort of memory usage bug, double-deletion or something. Use a debugger to figure out exactly which line it crashes on.   