Chinaunix首页 | 论坛 | 博客
  • 博客访问: 51920
  • 博文数量: 17
  • 博客积分: 651
  • 博客等级: 上士
  • 技术积分: 200
  • 用 户 组: 普通用户
  • 注册时间: 2010-12-23 14:23
文章分类

全部博文(17)

文章存档

2011年(10)

2010年(7)

我的朋友

分类: LINUX

2011-01-11 15:44:02

These only exist for inserting some debugging information which normally a
compiler would (could) take care of. CFI stands for Call Frame Information
and helps a debugger create a reliable backtrace through functions.

This has potential value for looking at the kernel with debuggers such as
GDB and NLKD and potential value inside the kernel itself when somebody
ports a DWARF unwinder to the kernel proper (DWARF is the debugging format
CFI is a part of) which google shows some are contemplating.

If you look at CFI_ADJUST_CFA_OFFSET you see it turn into an assembler
pesudo op that you could, as it advices, learn more about in info as.

You also see that without CONFIG_UNWIND_INFO, they turn into whitespace and
given that at least currently CONFIG_UNWIND_INFO is a dead config variable
you may conclude that it's currently fairly safe not too worry about them.
Robert Day tried to remove the macro defintions a while ago it seems so he
may have further information in the form of people telling him why they
wanted them to stay.

阅读(1720) | 评论(0) | 转发(0) |
0

上一篇:asmlinkage

下一篇:2 > &1

给主人留下些什么吧!~~