systemtap fails to compile simple tapsets

Bug #838205 reported by Serge Hallyn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemtap (Ubuntu)
Fix Released
High
Unassigned

Bug Description

When I compile a simple tapset, I get

root@domU-12-31-39-14-F0-B3:~/tapset# stap --vp 0001 m2.stap
In file included from /tmp/stap48rJgj/stap_012a6d41efc4903a84d9ebac5d381d79_3539.c:56:0:
/usr/share/systemtap/runtime/stack.c:98:2: error: unknown field ‘warning’ specified in initializer
/usr/share/systemtap/runtime/stack.c:98:2: error: initialization from incompatible pointer type [-Werror]
/usr/share/systemtap/runtime/stack.c:98:2: error: (near initialization for ‘print_stack_ops.address’) [-Werror]
/usr/share/systemtap/runtime/stack.c:99:2: error: unknown field ‘warning_symbol’ specified in initializer
/usr/share/systemtap/runtime/stack.c:99:2: error: initialization from incompatible pointer type [-Werror]
/usr/share/systemtap/runtime/stack.c:99:2: error: (near initialization for ‘print_stack_ops.stack’) [-Werror]
cc1: all warnings being treated as errors

make[1]: *** [/tmp/stap48rJgj/stap_012a6d41efc4903a84d9ebac5d381d79_3539.o] Error 1
make: *** [_module_/tmp/stap48rJgj] Error 2
Pass 4: compiled C into "stap_012a6d41efc4903a84d9ebac5d381d79_3539.ko" in 2960usr/1030sys/4613real ms.
Pass 4: compilation failed. Try again with another '--vp 0001' option.

The tapset is:

root@domU-12-31-39-14-F0-B3:~/tapset# stap --vp 0001 m2.stap
In file included from /tmp/stap48rJgj/stap_012a6d41efc4903a84d9ebac5d381d79_3539.c:56:0:
/usr/share/systemtap/runtime/stack.c:98:2: error: unknown field ‘warning’ specified in initializer
/usr/share/systemtap/runtime/stack.c:98:2: error: initialization from incompatible pointer type [-Werror]
/usr/share/systemtap/runtime/stack.c:98:2: error: (near initialization for ‘print_stack_ops.address’) [-Werror]
/usr/share/systemtap/runtime/stack.c:99:2: error: unknown field ‘warning_symbol’ specified in initializer
/usr/share/systemtap/runtime/stack.c:99:2: error: initialization from incompatible pointer type [-Werror]
/usr/share/systemtap/runtime/stack.c:99:2: error: (near initialization for ‘print_stack_ops.stack’) [-Werror]
cc1: all warnings being treated as errors

make[1]: *** [/tmp/stap48rJgj/stap_012a6d41efc4903a84d9ebac5d381d79_3539.o] Error 1
make: *** [_module_/tmp/stap48rJgj] Error 2
Pass 4: compiled C into "stap_012a6d41efc4903a84d9ebac5d381d79_3539.ko" in 2960usr/1030sys/4613real ms.
Pass 4: compilation failed. Try again with another '--vp 0001' option.

The following upstream bug: http://comments.gmane.org/gmane.linux.systemtap/17948
points to an upstream fix, though I have not yet tested that.

Tags: patch

Related branches

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I just compiled a package with the fixing commit cherrypicked, and it worked. It did require some extra patching to get around variable-set-but-not-used errors though.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
tags: added: patch
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

(Taking the liberty of setting 'triaged' as upstream confirms the problem and the fix, and high priority as it leaves systemtap unusable while unfixed)

Changed in systemtap (Ubuntu):
status: New → Triaged
importance: Undecided → High
Changed in systemtap (Ubuntu):
status: Triaged → Confirmed
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemtap - 1.4-1ubuntu2

---------------
systemtap (1.4-1ubuntu2) oneiric; urgency=low

  * debian/patches/fix-compile-warning: Apply upstream fix for failure to
    compile tapsets due to kernel change. (LP: #838205)
  * debian/patches/no-werror.patch: Remove -Werror from CFLAGS to avoid
    new variable-set-but-not-used errors when building.
 -- Ubuntu <email address hidden> Wed, 31 Aug 2011 16:06:54 +0000

Changed in systemtap (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.