在程序允许崩溃后,会生成core文件,通过core文件和对应的可执行文件以及其链接的库文件,可以通过gdb解析出程序崩溃最后的堆栈信息,但是这些信息显示时,不一定是程序运行到当前栈帧位置时变量就是那样的,有可能是经过后面的运行才变成栈帧看到的样子的。以下面一个小demo验证一下
#include <stdio.h>
#include <iostream>
using namespace std;
class Myclass {
public:
Myclass() { my_errno = 0;};
~Myclass() {};
void SetErrno(int no)
{
my_errno = no;
}
private:
int my_errno;
};
int dodododo(Myclass * p_myclass)
{
p_myclass->SetErrno(3);
cout<<"test"<<endl;
return 0;
}
int dododo(Myclass * p_myclass)
{
p_myclass->SetErrno(2);
dodododo(p_myclass);
return 0;
}
int donothing(Myclass * p_myclass)
{
p_myclass->SetErrno(1);
dododo(p_myclass);
return 0;
}
void dodododo()
{
cout<<"donothing"<<endl;
}
int main()
{
Myclass myclass;
myclass.SetErrno(0);
donothing(&myclass);
dodododo();
return 1;
}
编译:gdb -g test.cp -o test
gdb调试程序:gdb test
进入到gdb后,先打三个断点,分别打在
dododo(p_myclass);
dodododo(p_myclass);
cout<<"test"<<endl;
这三个位置,随后start,每运行停止一次,bt full查看堆栈信息,可以看到如下结果。
Breakpoint 1, donothing (p_myclass=0x7fffffffe7e0) at test.cpp:33
33 dododo(p_myclass);
(gdb) bt full
#0 donothing (p_myclass=0x7fffffffe7e0) at test.cpp:33
No locals.
#1 0x0000000000400a51 in main () at test.cpp:44
myclass = {my_errno = 1}
Breakpoint 2, dododo (p_myclass=0x7fffffffe7e0) at test.cpp:27
27 dodododo(p_myclass);
(gdb) bt full
#0 dododo (p_myclass=0x7fffffffe7e0) at test.cpp:27
No locals.
#1 0x00000000004009f6 in donothing (p_myclass=0x7fffffffe7e0) at test.cpp:33
No locals.
#2 0x0000000000400a51 in main () at test.cpp:44
myclass = {my_errno = 2}
Breakpoint 3, dodododo (p_myclass=0x7fffffffe7e0) at test.cpp:21
21 cout<<"test"<<endl;
(gdb) bt full
#0 dodododo (p_myclass=0x7fffffffe7e0) at test.cpp:21
No locals.
#1 0x00000000004009c6 in dododo (p_myclass=0x7fffffffe7e0) at test.cpp:27
No locals.
#2 0x00000000004009f6 in donothing (p_myclass=0x7fffffffe7e0) at test.cpp:33
No locals.
#3 0x0000000000400a51 in main () at test.cpp:44
myclass = {my_errno = 3}
可以看到,随着程序的运行,main层的myclass变量在堆栈里面的内容是动态变化的,所以可以得出,对应的栈帧信息的显示,不一定是运行到哪里就是那样的,而只能说明,程序最后core掉的时候,变量是那个结果。