Re: "no match" semantic error for some existing probe points

["Gui,Jian" <guij at cn dot ibm dot com>]

> There should be a DW_TAG_inlined_subroutine containing this PC range.
> That should have DW_AT_call_{file,line} attributes that say ptrace.c
> line 248.  If the compiler is producing this info, then we could
> potentially make systemtap use it.  The structure of DWARF information
> unfortunately does not make this especially easy.
Thanks, Roland. From the debug_info of vmlinux:
 <1><4670f>: Abbrev Number: 47 (DW_TAG_subprogram)
     DW_AT_sibling     : <467d3>
     DW_AT_external    : 1
     DW_AT_name        : (indirect string, offset: 0x4aa5): 
ptrace_disable
     DW_AT_decl_file   : 1
     DW_AT_decl_line   : 246
     DW_AT_prototyped  : 1
     DW_AT_low_pc      : 0x9db0
     DW_AT_high_pc     : 0x9dec
     DW_AT_frame_base  : 1 byte block: 51       (DW_OP_reg1)
 <2><4672e>: Abbrev Number: 48 (DW_TAG_formal_parameter)
     DW_AT_name        : (indirect string, offset: 0x146c): child
     DW_AT_decl_file   : 1
     DW_AT_decl_line   : 245
     DW_AT_type        : <410d2>
     DW_AT_location    : 1 byte block: 53       (DW_OP_reg3)
 <2><4673b>: Abbrev Number: 49 (DW_TAG_inlined_subroutine)
     DW_AT_abstract_origin: <467d3>
     DW_AT_low_pc      : 0x9db0
     DW_AT_high_pc     : 0x9de8
     DW_AT_call_file   : 0
     DW_AT_call_line   : 0

Does this mean the compiler didn't produce such information and
we cannot handle this in systemtap?

Thanks.

-Guijian