public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: buddhika chamith <chamibuddhika@gmail.com>
To: David Smith <dsmith@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sourceware.org
Subject: Re: Systemtap user space probing issue - Unknown symbol in module
Date: Thu, 21 Jul 2016 15:10:00 -0000	[thread overview]
Message-ID: <CAPO7Hz_n6rjRFAEGSAb51X7-B=O64boD7pNCK7Gg8H5r0Ju6ww@mail.gmail.com> (raw)
In-Reply-To: <74ec06df-cc13-4d42-d333-38a5039112e7@redhat.com>

Thanks. There is an older installation of systemtap in the system as
well. But I made sure that I was using the later version when running
these commands. I will uninstall the older version and see just in
case. And I will follow up with the perf output if that doesn't work
out as well.

On Tue, Jul 19, 2016 at 2:32 PM, David Smith <dsmith@redhat.com> wrote:
> On 07/19/2016 10:47 AM, buddhika chamith wrote:
>> Please find it attached. I don't have sudo access to this particular
>> machine at the moment. But let me know if this is not enough
>> information without running as root.
>>
>> On Tue, Jul 19, 2016 at 11:30 AM, Frank Ch. Eigler <fche@redhat.com> wrote:
>>>
>>> chamibuddhika wrote:
>>>
>>>> [...]
>>>> [7681057.827483] stap_610f349f374e883560aeeb9de1523c1f__13285: Unknown
>>>> symbol __tracepoint_sched_process_exit (err 0)
>>>> [...]
>>>
>>> This is reminiscent of
>>> https://www.sourceware.org/ml/systemtap/2016-q2/msg00082.html but
>>> those incompatibilities were worked out in a stap version << 3.0.
>>> Could you submit a fuller 'stap-report' output?
>
> What's odd is that according to your 'stap-report' output, your kernel
> has CONFIG_TRACEPOINTS=y, but systemtap can't register the tracepoints
> it needs.
>
> Can you try 'perf list tracepoint' as root and see what you get?
>
> One more thing. You said earlier you were running systemtap 3.0. It
> appears that you have systemtap 2.3 installed. Did you build systemtap
> 3.0 yourself?
>
> --
> David Smith
> dsmith@redhat.com
> Red Hat
> http://www.redhat.com
> 256.217.0141 (direct)
> 256.837.0057 (fax)

  reply	other threads:[~2016-07-21 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18 10:58 buddhika chamith
2016-07-18 18:11 ` David Smith
2016-07-19 15:01   ` buddhika chamith
2016-07-19 15:09     ` buddhika chamith
2016-07-19 15:30       ` Frank Ch. Eigler
2016-07-19 15:47         ` buddhika chamith
2016-07-19 18:32           ` David Smith
2016-07-21 15:10             ` buddhika chamith [this message]
2016-07-18 18:26 ` Josh Stone

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='CAPO7Hz_n6rjRFAEGSAb51X7-B=O64boD7pNCK7Gg8H5r0Ju6ww@mail.gmail.com' \
    --to=chamibuddhika@gmail.com \
    --cc=dsmith@redhat.com \
    --cc=fche@redhat.com \
    --cc=systemtap@sourceware.org \
    /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).