Ack! I thought it was that program because the compiler was working fine yesterday, and just today when I start this new one it starts crashing. However, the compiler is crashing now even when I compile my other project.
Alright, so I can scratch the "Is there some mysterious my-code-runs-at-compile magic going on" question and move on to "What causes my compiler to break overnight?"
I have started on another project, this one a fun memory editor for an old game I play. I have a process class in which I've defined functions to get the process IDs for windows and read memory from them (haven't gotten to writing memory yet).
Anyway, the problem is actually that the target window (I have it hard-coded to call process.setup("FCE Ultra") first thing in main()) freezes, but not at runtime; it freezes when I compile. And sometimes, when I have that window up during compile, the compiler program itself freezes too.
I'm using Bloodshed's Dev-C++ compiler.
What is the deal? Does the compiler actually run parts of the code at compile time?
When I actually do get it to compile, if I run the program itself that has been created it works fine. It just crashes the target window and the compiler when I try to compile the program. It's getting annoying having to continually go to the program manager, tell it to forcibly close the windows, and then restart them all the time.
Actually, upon further testing, the compiler is crashing often even when the target program is not running.
Could it actually be my code that is somehow crashing the compiler?