Stack around the variable 'theAnalysis' was corrupted
Moderators: silvia, selimgunay, Moderators
Stack around the variable 'theAnalysis' was corrupted
Hi,
I try to use QuickMain example code in a method of my own class.
because I don't have exit(0) added, The debug message is:
"Stack around the variable 'theAnalysis' was corrupted."
Can anybody tell me how to solve it?
Thanks
I try to use QuickMain example code in a method of my own class.
because I don't have exit(0) added, The debug message is:
"Stack around the variable 'theAnalysis' was corrupted."
Can anybody tell me how to solve it?
Thanks
-
- Posts: 50
- Joined: Mon Jun 18, 2007 1:10 am
- Location: ROMA
i have just built and executed the code using what is available in cvs. it works.
there was a minor change, but that should have stopped the compiler from building the .exe, which is not the problem you two have described.
can you try building using the source code available in cvs to see if the problem you describe still exists.
there was a minor change, but that should have stopped the compiler from building the .exe, which is not the problem you two have described.
can you try building using the source code available in cvs to see if the problem you describe still exists.
-
- Posts: 50
- Joined: Mon Jun 18, 2007 1:10 am
- Location: ROMA
-
- Posts: 1
- Joined: Sun Jul 14, 2013 9:41 am
- Location: None
Re: Stack around the variable 'theAnalysis' was corrupted
Ehm sorry for bringing this up again, but I get exactly the same error. And it is definitely an error, calling the exit function is just plain wrong as it skips the destructors of your objects. For that matter, you should let the stack nicely unwind itself, just return 0 at the end of the main function. Of course the release version makes the error message go away since the stack is not checked anymore, this doesn't mean that the error is gone...
I caught this error running \EXAMPLES\Example1\main.cpp. Also, there are memory leaks.
I caught this error running \EXAMPLES\Example1\main.cpp. Also, there are memory leaks.