From: beginner966 <nitin966@gmail.com>
To: systemtap@sourceware.org
Subject: Help required in relation with static probe points, STAP_MARK
Date: Thu, 15 Jan 2009 17:23:00 -0000 [thread overview]
Message-ID: <21481846.post@talk.nabble.com> (raw)
Hi,
I am a beginner and was trying to use STAP_MARK to create static probe
points in kernel/sched.c. When I patched the sched.c file and did a make,
following errors were obtained:
kernel/sched.c: In function âadd_preempt_countâ:
kernel/sched.c:4425: warning: unused variable âparent_eipâ
kernel/sched.c:4424: warning: unused variable âeipâ
kernel/sched.c: In function â__migrate_taskâ:
kernel/sched.c:6295: error: implicit declaration of function âSTAP_MARKâ
kernel/sched.c:6295: error: âcpu_offlineâ undeclared (first use in this
function)
kernel/sched.c:6295: error: (Each undeclared identifier is reported only
once
kernel/sched.c:6295: error: for each function it appears in.)
kernel/sched.c:6311: error: âalready_movedâ undeclared (first use in this
function)
kernel/sched.c:6317: error: âaffinity_changedâ undeclared (first use in this
function)
kernel/sched.c:6326: error: âmigration_successâ undeclared (first use in
this function)
Which header file is to be included for STAP_MARK to work ?
Please reply. Thanks !
--
View this message in context: http://www.nabble.com/Help-required-in-relation-with-static-probe-points%2C-STAP_MARK-tp21481846p21481846.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.
next reply other threads:[~2009-01-15 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 17:23 beginner966 [this message]
2009-01-15 18:56 ` David Smith
2009-01-16 9:44 ` beginner966
2009-01-16 9:59 ` beginner966
2009-01-17 15:23 ` Frank Ch. Eigler
2009-01-17 16:35 ` beginner966
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=21481846.post@talk.nabble.com \
--to=nitin966@gmail.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).