Compile crashes certain windows

(update)
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?"
(/update)

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?

Quote:

---

Does the compiler actually run parts of the code at compile time?

---

Excluding weird compilers, No! it does not run code!

I'm not sure what you mean by target window. If the compiler crashes have you tried compiling other programs?

Yes, and at first it was compiling just fine when I try it on my other project. However, I just updated my original post at the same time you replied; apparently, it is crashing on the other project now, so I've ruled out the wierd compiler-executes-code conspiracy theory.

And by target window, I mean the window it is targetting to read/write the memory for. In this case, I'm targetting a window named "FCE Ultra" so I can read its memory process.

Well, sounds like something has been corrupted in the compiler. Your best bet would be to reinstall it (usually easier than tracking down the problem).

Quote:

---

Originally Posted by Magos

Well, sounds like something has been corrupted in the compiler. Your best bet would be to reinstall it (usually easier than tracking down the problem).

---

Alright, I just tried that and it's still screwed up.

Is it possible that the compiler after corruption could have corrupted the project files? Should I try recreating the projects from scratch, copy the code from the old files into new files, and recompile fresh like that? Or wouldn't that make a difference?

I can't think of anything else.

When a program is uninstalled, that does not necesarily mean that all its files are removed. Therefore, you could end up uninstalling Dev C++ and not getting all the files, some of which could be corrupted. Do you have another computer you could use to test and see if the project files themselves are corrupted?

If you don't have another computer at your disposal, try, like you said, rebuilding the project files, or you could uninstall Dev C++, and then start searching your hard drive for any straggler files that managed to get by the uninstall process.