Wow. This is new to me. EVIL STL!

Wow. This has me stumped. Does ANYBODY know wtf this error means? Is there anything i can do about? This is the work of the evil standard template lib. i just know it.


--------------------Configuration: driver - Win32 Debug------------------
Compiling...
driver.cpp
c:\comp2.h(38) : fatal error C1001: INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1794)
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
Error executing cl.exe.

driver.exe - 1 error(s), 0 warning(s)

......Stupid Vectors Did This To Me..........

tried re-installing?

The most common causes are a forgotten ; at the end of a class definition or forgotten }'s msvc crashes quite easily. The only way to fix this is to comment out most of your code and gradually increase it to see what's causing the bug.

thx for the help guys, i found the problem. it was in the overloaded insertion operator i was using to output a vector of employees. it compiles now but has a runtime error. im oing to have a debugging party later today to watch memory and see wtf is going on.

:) There's a mysterious problem with the computers at my school, where if one user logs into a computer too many times, MSVC++ will always throw that error at you when you try to build, even if the code is perfect.

Quote:

---

Originally posted by grib
The most common causes are a forgotten ; at the end of a class definition or forgotten }'s

---

None of them, I know what it says on these errors, And its not
compiler error. Could you post the the line where the error's
found?

Quote:

---

msvc crashes quite easily

---

Do you know a compiler that runs when you forget a ';' or '}'?

Quote:

---

Originally posted by Travis Dane

Do you know a compiler that runs when you forget a ';' or '}'?

---

msvc is the only compiler I've ever used that actually crashes on things like that. Most compilers (many gcc's ATT c++ under solaris,intel's compiler, watcom and borland) will simply generate a large number of errors as just about every statement thereafter will be wrong. Msvc usually catches this and does not crash, it's just that when it crashes, in my expereance, that's what does it.

MSVC din't crash! It give an internal compiler error! What do you
call crash? I call a program not able to run futher a crash, That's
not in this situation. Again post the code we still don't know on
what kind of mistake wheyre talking about.

An internal compiler error is a crash, it's not an error in the code you are compiling (though that is the most common cause) it is the compiler itself no longer being able to function. " (compiler file 'msc1.cpp', line 1794) " is a line in the source for msvc itself, not the original posters code.

Well, in all the time I've been using MSVC++, I've never ever had it crash for something like that. In fact, the only times I've had it crash are:

a) Illegal operation: When my whole system is screwed up anyways
b) Internal compiler error: What I said above (about logging in too many times with one user)
c) Illegal operation: When I run a program in the debugger, then close the program with Ctrl-Alt-Delete. Then I get an illegal operation, but then you're not supposed to do that anyways...

Quote:

---

Originally posted by grib
An internal compiler error is a crash, it's not an error in the code you are compiling (though that is the most common cause) it is the compiler itself no longer being able to function. " (compiler file 'msc1.cpp', line 1794) " is a line in the source for msvc itself, not the original posters code.

---

Then he messed something up in MSVC++, Because it has NEVER
did this with me.

Quote:

---

An internal compiler error is a crash, it's not an error in the code you are compiling (though that is the most common cause) it is the compiler itself no longer being able to function. " (compiler file 'msc1.cpp', line 1794) " is a line in the source for msvc itself, not the original posters code.

---

An internal compiler error isn't a crash. It's when the compiler is unable to recover its state after it detects an error, you would have known that if you'd looked up the error number on msdn.microsoft.com. I've been generating those errors using the vector class for ages, and it's always because I do something wrong, not the compiler. You won't ever get that unless you've made an error, so moofangoo to you too

Quote:

---

You won't ever get that unless you've made an error

---

Wrong, you might but it won't be the compiler's fault ;)

Yeah I guess you're right, because it also describes errors occuring because of certain settings of the compiler, which may not necessarily be your fault. I still believe those to be mostly generated by errors in the code, for that's how I've always generated them (and I've generated a lot with the vector class).