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


> The tcptest.stp failed on most of the platforms. When trying to
compile
> the script by hand it gets a number of errors:
> 	"failed to retrieve return value location: identifier '$return'"
>
> For
> install/share/systemtap/tapset/tcp.stp:159:9
> install/share/systemtap/tapset/tcp.stp:129:9
>
> This is looking like there might be a problem with the
> debuginformation for some of the kernels.
>
> -Will

I could not reproduce any "$return" error on my boxes (ia32 & x86_64).
Looks like Bibo also had this problem earlier, not sure if he still sees
the issue, or if any resolution has been made.  See the thread below.

http://sourceware.org/ml/systemtap/2006-q3/msg00130.html

http://sourceware.org/ml/systemtap/2006-q3/msg00129.html

On the other hand, I do see the tcp_test.exp fails occasionally when TCP
traffic on the test machine is really low, so the test itself may be
part of the problem.  I just need to twist tcp_test.exp to send/receive
more packets when it is executed.  This should reduce the number of
failure, and perhaps isolate the cases where the real "$return" errors
appear.

Thang

             reply	other threads:[~2006-10-18 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 12:04 Nguyen, Thang P [this message]
2006-10-18 13:51 ` William Cohen
2006-10-18 14:08 ` bibo,mao
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
2006-10-18 19:46 Nguyen, Thang P

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=9AE298E00BCF7B469C04BE82FCE78B8701AC12DC@scsmsx414.amr.corp.intel.com \
    --to=thang.p.nguyen@intel.com \
    --cc=systemtap@sourceware.org \
    --cc=wcohen@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).