public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: "Nguyen, Thang P" <thang.p.nguyen@intel.com>
Cc: systemtap@sourceware.org
Subject: Re: Summary of nightly testing 20061016 (failed to retrieve return  value location)
Date: Wed, 18 Oct 2006 19:26:00 -0000	[thread overview]
Message-ID: <45367FC4.2020400@redhat.com> (raw)
In-Reply-To: <9AE298E00BCF7B469C04BE82FCE78B8701AC14BF@scsmsx414.amr.corp.intel.com>

Nguyen, Thang P wrote:
> Hi Will,
> 
> Sorry for the confusion.  The test I used 
> 
> ./testsuite/systemtap.samples/tcptest.exp (tcptest.stp)
> 
> Occasionally it fails due to TCP traffic, but not "$return" error.
> 
> 
> Thang

The problem is due to shared libraries. Need to set up so looks for shared 
libraries in when running the tests. Below demonstrates the problem.

$ 
LD_LIBRARY_PATH=/home/wcohen/systemtap_write/obj/lib-elfutils:/home/wcohen/systemtap_write/obj/lib-elfutils/systemtap:$LD_LIBRARY_PATH 
  ./stap ../src/testsuite/systemtap.samples/tcptest.stp

Okay the following works:

$ LD_LIBRARY_PATH=/home/wcohen/systemtap_write/intall2/lib/systemtap ./stap 
../src/testsuite/systemtap.samples/tcptest.stp

This does not work:

$  ./stap ../src/testsuite/systemtap.samples/tcptest.stp semantic error: failed 
to retrieve return value location: identifier '$return' at 
/home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:129:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:159:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:129:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:159:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:129:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:159:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:129:9
semantic error: failed to retrieve return value location: identifier '$return' 
at /home/wcohen/systemtap_write/intall2/share/systemtap/tapset/tcp.stp:159:9
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

-Will

  parent reply	other threads:[~2006-10-18 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:41 Nguyen, Thang P
2006-10-18 15:57 ` William Cohen
2006-10-18 16:40 ` William Cohen
2006-10-18 19:26 ` William Cohen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-18 19:46 Nguyen, Thang P
2006-10-18 12:04 Nguyen, Thang P
2006-10-18 13:51 ` William Cohen
2006-10-18 14:08 ` bibo,mao

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=45367FC4.2020400@redhat.com \
    --to=wcohen@redhat.com \
    --cc=systemtap@sourceware.org \
    --cc=thang.p.nguyen@intel.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).