Bug 501795

Summary: sdt.h on powerpc Error: junk at end of line: `0'
Product: Red Hat Enterprise Linux 5 Reporter: Mark Wielaard <mjw>
Component: systemtapAssignee: Frank Ch. Eigler <fche>
Status: CLOSED ERRATA QA Contact: BaseOS QE <qe-baseos-auto>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: mjw, pmuller, sghosh
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 10:01:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark Wielaard 2009-05-20 18:37:28 UTC
The sdt.h (static dynamic trace markers) are broken on powerpc.
This is with systemtap 0.9.7.

The problem manifests itself when compiling any program using sdt.h for STAP_PROBE or DTRACE_PROBE macros as "Error: junk at end of line: `0'"

It was fixed by:

commit 78c9d72e18da2d5c930fb39460c236ea24fee423
Author: Mark Wielaard <mjw>
Date:   Wed May 20 12:39:57 2009 +0200

    PR10172 sdt.h on powerpc Error: junk at end of line: `0'
    
    * includes/sys/sdt.h (STAP_NOP): __powerpc__ doesn't want an extra 0.
    
    Tested-by: Mahesh Jagannath Salgaonkar <mahesh.ibm.com>

This can be tested by checking that the sdt.exp tests all succeed:

sudo make installcheck RUNTESTFLAGS=sdt.exp

This might (or might not) be an issue with ia64 and s390. This functionality depends on full uprobes support for the architecture. If that isn't available the static marker support will not be usable for that architecture and then this bug isn't an issue.

See the upstream bug for more details:
http://sourceware.org/bugzilla/show_bug.cgi?id=10172

Comment 7 errata-xmlrpc 2009-09-02 10:01:17 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1313.html