diff options
| author | Josh Stone <jistone@redhat.com> | 2009-10-05 17:41:30 -0700 |
|---|---|---|
| committer | Josh Stone <jistone@redhat.com> | 2009-10-05 19:21:29 -0700 |
| commit | 6b517475576ac5f2209e5231d14d0b8aa0b6a4d5 (patch) | |
| tree | a6a9bf02abb2723e9acef0290c2ef93ac83fd191 /testsuite/systemtap.base/const_value_func.c | |
| parent | 6e2d11625b991b4094c9f2cc04e30f8d00f711a6 (diff) | |
| download | systemtap-steved-6b517475576ac5f2209e5231d14d0b8aa0b6a4d5.tar.gz systemtap-steved-6b517475576ac5f2209e5231d14d0b8aa0b6a4d5.tar.xz systemtap-steved-6b517475576ac5f2209e5231d14d0b8aa0b6a4d5.zip | |
PR10726: Get the correct scope for statement(NUM)
The problem in this bug is that our statement(NUM) lookup was only
searching for the outermost function (not inlined) which contains the PC
in question. When that PC happens to be the beginning of the function
and also the beginning of an inline, the caching was using the wrong
variable scope.
The function/statement(NUM) lookup has been rewritten to bypass all of
the CU and function iteration, and just go straight to a getscopes(pc)
lookup, so it will now always use the innermost containing die for the
variable scope.
* tapsets.cxx (query_addr): New, short-circuit for numeric probes.
(dwarf_query::query_module_dwarf): Route num probes to query_addr.
(query_label): Assume now that we only need to handle _str probes.
(query_dwarf_inline_instance): Ditto.
(query_dwarf_func): Ditto.
(query_cu): Ditto.
Diffstat (limited to 'testsuite/systemtap.base/const_value_func.c')
0 files changed, 0 insertions, 0 deletions