From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/16378] in-kernel utrace problem with 2.6.32: implicit declaration of function 'do_each_thread' in task_finder.c
Date: Mon, 06 Jan 2014 15:38:00 -0000 [thread overview]
Message-ID: <bug-16378-6586-GZG3t5apzf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16378-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16378
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
I took a look at the openvz patch you mentioned in bug #11113. As part of the
sched.h changes in that patch, it does this:
-#define do_each_thread(g, t) \
- for (g = t = &init_task ; (g = t = next_task(g)) != &init_task ; ) do
+#define do_each_thread_all(g, t) \
+ for (g = t = &init_task ; (g = t = next_task_all(g)) != &init_task ; )
do
So, the openvz patch is the culprit here. You might try either changing all
references to 'do_each_thread' to 'do_each_thread_all' in systemtap or
#defining do_each_thread() to do_each_thread_all() (in runtime.h).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-01-06 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 23:24 [Bug runtime/16378] New: " fahadaliarshad at gmail dot com
2014-01-06 15:38 ` dsmith at redhat dot com [this message]
2014-01-13 1:10 ` [Bug runtime/16378] " fahadaliarshad at gmail dot com
2014-01-13 1:14 ` fahadaliarshad at gmail dot com
2014-01-13 17:30 ` dsmith at redhat dot com
2014-02-01 8:20 ` vchappell at 4wardsciences dot com
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=bug-16378-6586-GZG3t5apzf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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).