This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/9911] New: Systemtap is broken with linux-next 2.6.29-rc6-next-20090226
- From: "mahesh at linux dot vnet dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 27 Feb 2009 11:37:37 -0000
- Subject: [Bug runtime/9911] New: Systemtap is broken with linux-next 2.6.29-rc6-next-20090226
- Reply-to: sourceware-bugzilla at sourceware dot org
[root@llm27lp1 linux-next]# /usr/local/bin/stap --vp 0001 --vp 0001 -e 'probe
syscall.* { print ("here\n") exit() }'
Running make -C "/lib/modules/2.6.29-rc6-next-20090226/build"
M="/tmp/stapOzhxl0" modules >/dev/null
In file included from
/tmp/stapOzhxl0/stap_427480df5645d5ef9e8919ec2e90e32e_93928.c:43:
/usr/local/share/systemtap/runtime/stack.c:33:28: error: asm/stacktrace.h: No
such file or directory
In file included from
/tmp/stapOzhxl0/stap_427480df5645d5ef9e8919ec2e90e32e_93928.c:43:
/usr/local/share/systemtap/runtime/stack.c:84: error: variable ?print_stack_ops?
has initializer but incomplete type
/usr/local/share/systemtap/runtime/stack.c:85: error: unknown field ?warning?
specified in initializer
cc1: warnings being treated as errors
/usr/local/share/systemtap/runtime/stack.c:85: warning: excess elements in
struct initializer
/usr/local/share/systemtap/runtime/stack.c:85: warning: (near initialization for
?print_stack_ops?)
/usr/local/share/systemtap/runtime/stack.c:86: error: unknown field
?warning_symbol? specified in initializer
/usr/local/share/systemtap/runtime/stack.c:86: warning: excess elements in
struct initializer
/usr/local/share/systemtap/runtime/stack.c:86: warning: (near initialization for
?print_stack_ops?)
/usr/local/share/systemtap/runtime/stack.c:87: error: unknown field ?stack?
specified in initializer
/usr/local/share/systemtap/runtime/stack.c:87: warning: excess elements in
struct initializer
/usr/local/share/systemtap/runtime/stack.c:87: warning: (near initialization for
?print_stack_ops?)
/usr/local/share/systemtap/runtime/stack.c:88: error: unknown field ?address?
specified in initializer
/usr/local/share/systemtap/runtime/stack.c:88: warning: excess elements in
struct initializer
/usr/local/share/systemtap/runtime/stack.c:88: warning: (near initialization for
?print_stack_ops?)
/usr/local/share/systemtap/runtime/stack.c: In function ?_stp_stack_print_fallback?:
/usr/local/share/systemtap/runtime/stack.c:97: error: implicit declaration of
function ?dump_trace?
make[1]: *** [/tmp/stapOzhxl0/stap_427480df5645d5ef9e8919ec2e90e32e_93928.o] Error 1
make: *** [_module_/tmp/stapOzhxl0] Error 2
Pass 4: compiled C into "stap_427480df5645d5ef9e8919ec2e90e32e_93928.ko" in
3350usr/610sys/4645real ms.
Pass 4: compilation failed. Try again with another '--vp 0001' option.
Running rm -rf /tmp/stapOzhxl0
The linux-next git tree as of 20090226
[root@llm27lp1 linux-next]# git log | head
commit f5e8cca8e64476777c42f068eabf66ccc55c957b
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu Feb 26 19:16:43 2009 +1100
Add linux-next specific files for 20090226
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
commit c8b27915751c6b102cd766855bbf45338e8e9470
Merge: a7cebc0... 5164c03...
[root@llm27lp1 linux-next]#
And the systemtap is git head is top of the tree:
[root@llm27lp1 systemtap]# git log | head
commit a8394af5f2db2bbb57414ffa4d4fc260e2aac3e9
Author: Mark Wielaard <mjw@redhat.com>
Date: Wed Feb 25 17:11:51 2009 +0100
Guard _struct_sigaction32_u with ifdef CONFIG_COMPAT.
* tapset/aux_syscalls.stp (_struct_sigaction_u): Only needed and compiles
when CONFIG_COMPAT defined.
commit bec508deffdb39affbd6e93a7ce1d2c92d653a12
[root@llm27lp1 systemtap]#
--
Summary: Systemtap is broken with linux-next 2.6.29-rc6-next-
20090226
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mahesh at linux dot vnet dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=9911
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.