public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/11751] on s390x, externalvar.exp gets libdwfl failures
Date: Wed, 30 Jun 2010 16:33:00 -0000	[thread overview]
Message-ID: <20100630140116.18993.qmail@sourceware.org> (raw)
In-Reply-To: <20100624180716.11751.dsmith@redhat.com>


------- Additional Comments From dsmith at redhat dot com  2010-06-30 14:01 -------
> OK, so this is for all the variables in the library. We think we found, libvar
> in this case, at address 0x1a70, we try to translate it to a location
> expression, so we ask libdwfl about it to determine which dwfl module exactly it
> is in. But then dwfl_addrmodule fails for some reason (but without it setting an
> error code).
> 
> Could you try to build the libexternalvar.so as above (or just comment out the
> rm in the exp file) and see waht loc2c-test says about it?
> 
> $ ./loc2c-test testsuite/libexternalvar.so 0x1a70
> 
> $ ./loc2c-test testsuite/libexternalvar.so 0x1a70 libvar

After adding '-e', I get:

# ./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

-- 


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.

  parent reply	other threads:[~2010-06-30 14:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 20:31 [Bug translator/11751] New: " dsmith at redhat dot com
2010-06-28 19:26 ` [Bug translator/11751] " mjw at redhat dot com
2010-06-28 19:26 ` dsmith at redhat dot com
2010-06-28 20:36 ` dsmith at redhat dot com
2010-06-30 16:26 ` mjw at redhat dot com
2010-06-30 16:33 ` dsmith at redhat dot com [this message]
2010-06-30 16:44 ` mjw at redhat dot com
2010-06-30 17:02 ` dsmith at redhat dot com
     [not found] <bug-11751-6586@http.sourceware.org/bugzilla/>
2011-09-23 17:57 ` fche at redhat dot com
2013-09-10 16:50 ` dsmith at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100630140116.18993.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).