This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Resolving Module Functions


I managed to get farther now.  It now finds my function, but complains
like this:

----------
focused on module 'my_driver'
selected function my_function
probe my_function@/home/codemonkey/work/src/kernel/my_driver/memory.c:103
module=my_driver reloc=.text section=.text pc=0xc4cdc40
Eliding unused function error
Eliding unused function log
Eliding unused function modname
Eliding unused function print_stack
Eliding unused function probemod
Eliding unused function stp_print_binary
Eliding unused function symdata
Eliding unused function symname
Eliding unused function warn
WARNING: read-only local variable 'fn' (alternatives: called):
identifier 'fn' at ./allocs.stp:4:49
 source:    printf("%s %d\n", probefunc(), @count(called[fn]))
                                                         ^
Pass 2: analyzed script: 2 probe(s), 2 function(s), 1 embed(s), 1
global(s) in 7190usr/70sys/7262real ms.
Pass 3: using cached
/home/codemonkey/.systemtap/cache/91/stapconf_915277be8d26adae259c71e334465ff8_386.h
probe_1385 locks called[rw]
stap_dwarf_probe module[11]
stap_dwarf_probe section[6]
stap_dwarf_probe pp[126]
dump_unwindsyms my_driver index=0 base=0x10000
Found build-id in my_driver, length 20, end at 0x10024
semantic error: libdwfl failure (dwfl_module_relocate_address): No
such file or directory
Pass 3: translated to C into
"/tmp/stapwUm3Ia/stap_f18ca2f5001da60c68b0cf2a68385006_1986.c" in
40usr/40sys/72real ms.
Pass 3: translation failed.  Try again with another '--vp 001' option.


What have I messed up this time?

hehe

-Dave

On Thu, Apr 16, 2009 at 12:36 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
>> > It is as if the .ko files were built without debugging data.
>> > What does "readelf -S FOO.ko" say about .debug* sections?
>>
>> I see no debug sections . . . are they there by default? ?Or, is a
>> special flag needed to make them?
>
> If you don't have CONFIG_DEBUG_INFO=y, you can add EXTRA_CFLAGS := -g
> or somesuch to your module makefile.
>
> - FChE
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]