浅析vs2008中 Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
2014-10-18 00:32
417 查看
Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted该错误一般是:由于堆栈出错,或是溢出引起的。
在debug下,根据不同的对齐方式,可能会有为栈上自动变量周围分配了一些保护空间。如果发生栈溢出, 就会写到保护空间上去。这样栈溢出就能被检查出来。
可以通过设置:project->配置属性->c/c++->代码生成”改为基本运行时检查,在debug下在编译就不会在提示上述错误。编译会通过,但是并没有从根本上解决问题,建议查和
‘var’相关的代码,尤其是注意是否内存越界。另一个是在release下还是会报错的。
stack around the variable “XX” was corrupted.,中文翻译就是“在变量XX周围的堆栈已损坏”。后面在上网看了很多技术资料,发现大多数网站都有这样的文章:
Code:
把 project->配置属性->c/c++->代码生成->基本运行时检查 为 默认值 就不会报本异常。具体原因正在研究中。。。
如果改为其他就有exception。
exception有时是有道理的
// step 1
STRINGC2& STRINGC2::operator += (const char x)
{
// if (x == 0) return *this;
char ptr[1]; // max is 1 digit
ptr[0] = x;
ptr[1] = '/0';
*this += ptr; // off to step 2 and back
return *this; // step 4 crash
}
这个也会导致上述exception。
问题描述:
Problem
The following error message occurs when building on Test RealTIme environment with the cvisual7 TDP?
Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted.
Cause
Stack pointer corruption is caused writing outside the allocated buffer in stack memeory.
Solution
This kind of error is detected by setting /RTC1 compiler option from menu Project -> Settings -> Configuration properties -> Build -> Compiler -> Compiler flags when using TDP cvisual7 in IBM® Rational® Test RealTime environment.. This enables stack frame run-time error checking. For example, the following code may cause the above error messge.
#include <stdio.h>
#include <string.h>
#define BUFF_LEN 11 // 12 may fix the Run-Time Check Failure #2
int rtc_option_test(char * pStr);
int main()
{
char * myStr = "hello world";
rtc_option_test(myStr);
return 0;
}
int rtc_option_test(char * pStr)
{
char buff[BUFF_LEN];
strcpy(buff, pStr); //cause Run-Time Check Failure #2 - Stack around
//the variable 'buff' was corrupted.
return 0;
}
我也尝试了把“project->配置属性->c/c++->代码生成”改为基本运行时检查,就没有这样的错误了。关于MSDN的解释是在堆栈外面读写某数据。错误是名为RTC1的编译器检测的。又看了更多的技术文章,发现这样的错误是程序员在项目到了一定大的时候,它占用的堆栈量就比较大。我也深有体会。因为自己本来编写一个类,运行时没有错,但是在添加成员属性的时候,在其它方式不变的情况下就容易发生这样的错误。所以据此我猜应该是VS2005(2008)在内部就限定了堆栈的大小,当项目足够大的时候,就会溢出。
在debug下,根据不同的对齐方式,可能会有为栈上自动变量周围分配了一些保护空间。如果发生栈溢出, 就会写到保护空间上去。这样栈溢出就能被检查出来。
可以通过设置:project->配置属性->c/c++->代码生成”改为基本运行时检查,在debug下在编译就不会在提示上述错误。编译会通过,但是并没有从根本上解决问题,建议查和
‘var’相关的代码,尤其是注意是否内存越界。另一个是在release下还是会报错的。
stack around the variable “XX” was corrupted.,中文翻译就是“在变量XX周围的堆栈已损坏”。后面在上网看了很多技术资料,发现大多数网站都有这样的文章:
Code:
把 project->配置属性->c/c++->代码生成->基本运行时检查 为 默认值 就不会报本异常。具体原因正在研究中。。。
如果改为其他就有exception。
exception有时是有道理的
// step 1
STRINGC2& STRINGC2::operator += (const char x)
{
// if (x == 0) return *this;
char ptr[1]; // max is 1 digit
ptr[0] = x;
ptr[1] = '/0';
*this += ptr; // off to step 2 and back
return *this; // step 4 crash
}
这个也会导致上述exception。
问题描述:
Problem
The following error message occurs when building on Test RealTIme environment with the cvisual7 TDP?
Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted.
Cause
Stack pointer corruption is caused writing outside the allocated buffer in stack memeory.
Solution
This kind of error is detected by setting /RTC1 compiler option from menu Project -> Settings -> Configuration properties -> Build -> Compiler -> Compiler flags when using TDP cvisual7 in IBM® Rational® Test RealTime environment.. This enables stack frame run-time error checking. For example, the following code may cause the above error messge.
#include <stdio.h>
#include <string.h>
#define BUFF_LEN 11 // 12 may fix the Run-Time Check Failure #2
int rtc_option_test(char * pStr);
int main()
{
char * myStr = "hello world";
rtc_option_test(myStr);
return 0;
}
int rtc_option_test(char * pStr)
{
char buff[BUFF_LEN];
strcpy(buff, pStr); //cause Run-Time Check Failure #2 - Stack around
//the variable 'buff' was corrupted.
return 0;
}
我也尝试了把“project->配置属性->c/c++->代码生成”改为基本运行时检查,就没有这样的错误了。关于MSDN的解释是在堆栈外面读写某数据。错误是名为RTC1的编译器检测的。又看了更多的技术文章,发现这样的错误是程序员在项目到了一定大的时候,它占用的堆栈量就比较大。我也深有体会。因为自己本来编写一个类,运行时没有错,但是在添加成员属性的时候,在其它方式不变的情况下就容易发生这样的错误。所以据此我猜应该是VS2005(2008)在内部就限定了堆栈的大小,当项目足够大的时候,就会溢出。
相关文章推荐
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'cmd' was corrupted 的可能原因
- Run-Time Check Failure #2 - Stack around the variable 'XX‘ was corrupted 解决方法
- Run-Time Check Failure #2 - Stack around the variable 'XXX' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'a' was corrupted 解决方法
- Run-Time Check Failure #2 - Stack around the variable 'szNum' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted
- VS2008中Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted 错误解决方法
- Run-Time Check Failure #2 - Stack around the variable 'usval' was corrupted
- VS2008中Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted 错误解决方法
- VS2008中Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted 错误解决方法
- Run-Time Check Failure #2 - Stack around the variable 'buf' was corrupted
- Run-Time Check Failure #2 - Stack around the variable 'ucPriKey' was corrupt
- Run-Time Check Failure #2 - Stack around the variable 'cz' was corrupted.
- Run-Time Check Failure #2 - Stack around the variable 'xxx' was corrupted(待解决)
- vs c库连接 Mysql后, 关闭M时,提示 Run-Time Check Failure #2 - Stack around the variable 'mysql' was corrupted.
- Run-Time Check Failure #2 - Stack around the variable 'var' was corrupted