Function call stack view

avenli

Upstairs, judging from your sample program, do you have to automatically generate a symbol table.c when compiling, just like your global variable name_rcd[], and the symbol address is stored incrementally, before you can use this Way?

Is there another way to achieve it?

yy偶不会

There is no need to generate symbol, it will generate .pdb when link is in .map, but you have to find a way to figure out the format of .pdb

druboy

Learn

felixwoo

I don't know if there is such an API function, but I know it is very simple to implement:

Create a linked list, each node records the current function name (you can get the function name through the macro __FUNCTION__);

The specific implementation process is as follows
Each time a function is entered, a node is added; when the function is exited, the node is deleted

In this case, when each function is called, the previous node in the linked list indicates the function that called it, and the previous node indicates the last function that called it...By analogy, all the calling relationships are listed. Up

avenli

Your method upstairs is theoretically possible, but it is too troublesome... and adds a lot of unnecessary overhead.

As far as I know, vxworks should use a similar method toyy偶不会. In the process of compiling the entire system, a symbol table .c file is generated, and finally this .c file is also linked into the final generated file. When you trace the stack, you can find it in that table. I think the role of the table is more than just the trace stack. The command line system provided by vxworks allows us to call the function by entering the function name, which should also be the credit of the .c file. As for files such as pdb, map, etc., it should only be meaningful when searching manually.

ch1074856

mark

yy偶不会

.map is for people to see, .pdb is for debuggers, there are more things in it than you think, there are all kinds of data types, it should be the most convenient...
This is not very good, once the compiler optimization is turned on, the call stack cannot be obtained in this way, because many functions do not generate stack frames...

avenli

The landlord seems to have added that when it is not debugging, you only need to use functions to watch the trace stack during operation, and you will never let an executable file find its own pdb...

Compiler optimization will not be generated across the board

push bp
mov bp, sp

Well, I don't know how many levels of gcc optimization will start like this...

avenli

After checking, there is no mention of not building a stack frame in the various optimization instructions of gcc, and the test results also did not find the situation of not building a stack frame.
Will vc?

yy偶不会

The gcc compilation optimization is slightly worse. When cl -O2, almost all functions do not generate stack frames, unless the function calls _alloca ...

gcc -O3 -Os can actually generate the function int foo() {return f(); }:
pushl %ebp
movl %esp, %ebp
popl %ebp
jmp _r
I'm fainted, it seems that the version is too low, and it must be upgraded.....