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]

[Bug translator/11751] on s390x, externalvar.exp gets libdwfl failures


------- Additional Comments From mjw at redhat dot com  2010-06-30 14:08 -------
(In reply to comment #5)
> # ./loc2c-test -e testsuite/libexternalvar.so 0x1a70
> ./loc2c-test: dwfl_addrdie: address out of range
> # ./loc2c-test -e testsuite/libexternalvar.so 0x1a70 libvar
> ./loc2c-test: dwfl_addrdie: address out of range
> 
> > and what does eu-readelf say about the lib_call function?
> > 
> > $ eu-readelf -s testsuite/libexternalvar.so | grep lib_call
> 
> # eu-readelf -s testsuite/libexternalvar.so | grep lib_call
>    48: 000000000000062c     18 FUNC    LOCAL  DEFAULT       10 lib_call

thanks. so we "guessed" the address of the lib_call function wrongly. how odd. I
assume ./loc2c-test -e testsuite/libexternalvar.so 0x62c libvar does spit out
the location information for libvar?

Could you run stap -vvvvv -p4 -e 'probe
process("testsuite/libexternalvar.so").function("lib_call") { printf("libvar =
%d\n", $libvar); }' to see how/what/where we get that 0x1a70 address in the
first place?

-- 


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

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


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