[Bug runtime/6562] New: $SYSTEMTAP_DEBUGINFO_PATH does not work

["prasad at linux dot vnet dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

I tried to place the vmlinux image in a custom location from its
default path i.e. /usr/lib/debug/lib/modules/`uname -r`/vmlinux by
defining the variable SYSTEMTAP_DEBUGINFO_PATH, as stated in Bug#2151,
but couldn't get the stap script to resolve the symbols.

I have attached the logs I collected during my trial on a latest
F9 machine running SystemTap cloned today from git (elfutils is 0.133 -
packaged with F9).

I was able to get the script working from a shell where the variable
SYSTEMTAP_DEBUGINFO_PATH was not defined, and the vmlinux was in its
default location (On a side note, even with vmlinux in its default path
and SYSTEMTAP_DEBUGINFO_PATH defined with the same default path, the
script did not work).

Logs
-----
[root@prasadkr_t60p systemtap]# ./stap -vvvvvv
/home/prasadkr/Desktop/futexes.stp
SystemTap translator/driver (version 0.7/0.133 git branch master, commit
d9d3b3a1)
Copyright (C) 2005-2008 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Created temporary directory "/tmp/stapIpQMuI"
Searched '/usr/local/share/systemtap/tapset/i686/*.stp', found 2
Searched '/usr/local/share/systemtap/tapset/*.stp', found 39
Pass 1: parsed user script and 41 library script(s) in
280usr/10sys/298real ms.
semantic error: libdwfl failure (missing kernel 2.6.25.3-18.fc9.i686
i686 debuginfo): No such file or directory while resolving probe point
kernel.function("sys_futex")?
semantic error: no match while resolving probe point syscall.futex
parsed 'sys_futex' -> func 'sys_futex'
blacklist regexps:
blfn:
^(atomic_notifier_call_chain|default_do_nmi|__die|die_nmi|do_debug|do_general_protection|do_int3|do_IRQ|do_page_fault|do_sparc64_fault|do_trap|dummy_nmi_callback|flush_icache_range|ia64_bad_break|ia64_do_page_fault|ia64_fault|io_check_error|mem_parity_error|nmi_watchdog_tick|notifier_call_chain|oops_begin|oops_end|program_check_exception|single_step_exception|sync_regs|unhandled_fault|unknown_nmi_error|.*raw_.*lock.*|.*read_.*lock.*|.*write_.*lock.*|.*spin_.*lock.*|.*rwlock_.*lock.*|.*rwsem_.*lock.*|.*mutex_.*lock.*|raw_.*|.*seq_.*lock.*|atomic_.*|atomic64_.*|get_bh|put_bh|.*apic.*|.*APIC.*|.*softirq.*|.*IRQ.*|.*_intr.*|__delay|.*kernel_text.*|get_current|current_.*|.*exception_tables.*|.*setup_rt_frame.*|.*preempt_count.*|preempt_schedule)$
blfn_ret: ^(do_exit|sys_exit|sys_exit_group|__switch_to)$
blfile: ^(kernel/kprobes.c|arch/.*/kernel/kprobes.c)$
semantic error: no match while resolving probe point
syscall.futex.return
dwarf_builder releasing dwflpp
Pass 2: analyzed script: 1 probe(s), 0 function(s), 0 embed(s), 6
global(s) in 10usr/0sys/5real ms.
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.
Running rm -rf /tmp/stapIpQMuI
[root@prasadkr_t60p systemtap]#
[root@prasadkr_t60p systemtap]#
[root@prasadkr_t60p systemtap]#
[root@prasadkr_t60p systemtap]#
[root@prasadkr_t60p systemtap]# env | grep DEBUG
SYSTEMTAP_DEBUGINFO_PATH=/home/prasadkr/tryvmlinux/
[root@prasadkr_t60p systemtap]# ls -lh /home/prasadkr/tryvmlinux/
total 72M
-rwxr-xr-x 1 root root 72M 2008-05-13 15:17 vmlinux
[root@prasadkr_t60p systemtap]#
[root@prasadkr_t60p systemtap]# ls -l
/usr/lib/debug/lib/modules/2.6.25.3-18.fc9.i686/
total 73288
drwxr-xr-x 9 root root     4096 2008-05-15 19:34 kernel
drwxr-xr-x 2 root root     4096 2008-05-15 19:34 vdso
-rwxr-xr-x 1 root root 74957069 2008-05-24 23:25 vmlinux
[root@prasadkr_t60p systemtap]#

-- 
           Summary: $SYSTEMTAP_DEBUGINFO_PATH does not work
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: prasad at linux dot vnet dot ibm dot com
                CC: prasad at linux dot vnet dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=6562

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.