From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: William Cohen <wcohen@redhat.com>
Cc: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
systemtap@sources.redhat.com
Subject: Re: testsuits on IA64
Date: Wed, 09 Nov 2005 17:51:00 -0000 [thread overview]
Message-ID: <20051109095130.A32424@unix-os.sc.intel.com> (raw)
In-Reply-To: <437210C8.9020908@redhat.com>; from wcohen@redhat.com on Wed, Nov 09, 2005 at 10:07:52AM -0500
On Wed, Nov 09, 2005 at 10:07:52AM -0500, William Cohen wrote:
> Keshavamurthy Anil S wrote:
>
> I don't have a ia64 machine handy to try things out on. Could you send
> me the output that comes on the console from "stap -v -k
> ./systemtap.base/kmodule.stp"? I would like to see that error messages
> the compiler is producing when it attempts to produce the module.
Hi Will,
Here goes the output you requested, as mentioned earlier I don't have any problems
running individual tap scripts manually. It is only when I run runtest I see timeouts.
Thanks,
Anil
[root@csdor-tiger1 testsuite]# stap -v -k systemtap.base/kmodule.stp
Created temporary directory "/tmp/stapLpQ3QC"
Searched '/usr/local/share/systemtap/tapset/2.6.9-22.10.EL/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6.9/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/*.stp', match count 9
Pass 1: parsed user script and 9 library script(s).
parsed 'ext3_sync_file' -> func 'ext3_sync_file'
pattern 'ext3' matches module 'ext3'
focused on module 'ext3' = [a00000020014c000-a000000200192db8, bias 0]
pattern 'ext3_sync_file' matches function 'ext3_sync_file'
selected function ext3_sync_file
prologue disagreement: ext3_sync_file heur0=a000000200153981 heur1=a000000200153982
querying entrypc of function 'ext3_sync_file'
Pass 2: analyzed user script. 3 probe(s), 10 function(s), 1 global(s).
Running grep " [tT] " /proc/kallsyms | sort -k 1,16 -s -o /tmp/stapLpQ3QC/symbols.sorted
Pass 3: translated to C into "/tmp/stapLpQ3QC/stap_15614.c"
Running make -C "/lib/modules/2.6.9-22.10.EL/build" M="/tmp/stapLpQ3QC" modules
make: Entering directory `/usr/src/kernels/2.6.9-22.10.EL-ia64'
CC [M] /tmp/stapLpQ3QC/stap_15614.o
Building modules, stage 2.
MODPOST
CC /tmp/stapLpQ3QC/stap_15614.mod.o
LD [M] /tmp/stapLpQ3QC/stap_15614.ko
make: Leaving directory `/usr/src/kernels/2.6.9-22.10.EL-ia64'
Pass 4: compiled into "stap_15614.ko"
Running sudo /usr/local/libexec/systemtap/stpd -r /tmp/stapLpQ3QC/stap_15614.ko
systemtap starting probe
next prev parent reply other threads:[~2005-11-09 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 23:21 Keshavamurthy, Anil S
2005-11-04 23:47 ` Hien Nguyen
2005-11-08 16:14 ` William Cohen
2005-11-08 16:27 ` William Cohen
2005-11-09 0:17 ` Keshavamurthy Anil S
2005-11-09 15:07 ` William Cohen
2005-11-09 17:51 ` Keshavamurthy Anil S [this message]
2005-11-09 19:26 ` William Cohen
2005-11-09 19:47 ` Keshavamurthy Anil S
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 10:08 Mao, Bibo
2005-11-04 18:57 Keshavamurthy, Anil S
2005-11-04 19:00 ` Frank Ch. Eigler
2005-11-04 19:09 ` Keshavamurthy Anil S
2005-11-04 19:13 ` Frank Ch. Eigler
2005-11-04 23:04 ` William Cohen
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=20051109095130.A32424@unix-os.sc.intel.com \
--to=anil.s.keshavamurthy@intel.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--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).