Run-Time Check Failure #2 - Stack around the variable 'novouser' was corrupted.

IndioDoido · 05-22-2007, 04:18 PM

hi!

when i', running my C project it gives me this error:

- Run-Time Check Failure #2 - Stack around the variable 'novouser' was corrupted.

This error apears when i change my actual username for a new one. But if i say ignore on the error in the message box, the program continues and the new username is saved :-S

??

Adak · 05-22-2007, 05:17 PM

As you may know, the stack is that area that deals with parameter passing, amongst other things. IMO it's a serious warning, and definitely worth fixing.

For anything more than general hints, you'll have to post up your code.

vart · 05-22-2007, 11:09 PM

probably - you have a buffer that is not big enough to store the new name... You SHOULD fix this error.

**Salem** · 05-22-2007, 11:42 PM

The compiler in debug mode has added padding around variables to detect when you overrun the allocated space.
In a release build, you'll have no such safety net and a real hard crash could be mere moments away.

vart is right, you need to fix this ASAP.

05-22-2007, 04:18 PM	#1
IndioDoido Registered User Join Date: Apr 2007 Posts: 194	Run-Time Check Failure #2 - Stack around the variable 'novouser' was corrupted. hi! when i', running my C project it gives me this error: - Run-Time Check Failure #2 - Stack around the variable 'novouser' was corrupted. This error apears when i change my actual username for a new one. But if i say ignore on the error in the message box, the program continues and the new username is saved :-S ?? __________________ "Artificial Intelligence usually beats natural stupidity."
IndioDoido is offline

05-22-2007, 11:09 PM	#3
vart CSharpener Join Date: Oct 2006 Posts: 5,556	probably - you have a buffer that is not big enough to store the new name... You SHOULD fix this error. __________________ If I have eight hours for cutting wood, I spend six sharpening my axe.
vart is offline

05-22-2007, 11:42 PM	#4
Salem and the hat of Destiny Join Date: Aug 2001 Location: The edge of the known universe Posts: 22,495	The compiler in debug mode has added padding around variables to detect when you overrun the allocated space. In a release build, you'll have no such safety net and a real hard crash could be mere moments away. vart is right, you need to fix this ASAP. __________________ If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
Salem is offline

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
The Timing is incorret	Drew	C++ Programming	5	08-28-2003 04:57 PM
inputting time in separate compilation	sameintheend01	C++ Programming	6	03-13-2003 04:33 AM
I apologize. Good bye.	doubleanti	A Brief History of Cprogramming.com	14	05-03-2002 06:51 PM
Create class at run time	muaed	A Brief History of Cprogramming.com	3	04-11-2002 08:13 AM
Stack functions as arrays instead of node pointers	sballew	C Programming	8	12-04-2001 11:13 AM

05-22-2007, 05:17 PM	#2
Adak Registered User Join Date: Sep 2006 Posts: 3,720	As you may know, the stack is that area that deals with parameter passing, amongst other things. IMO it's a serious warning, and definitely worth fixing. For anything more than general hints, you'll have to post up your code.
Adak is offline