This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Unknown symbol error using stap in RHEL 5.4


Maynard Johnson <maynardj@us.ibm.com> writes:

> [...]  *Frank*, the tweak I mentioned above was this: The stapitrace
> rpm installation adds a tapset script to
> /usr/share/systemtap/tapsets/ppc64.  I found that with the updated
> systemtap, I needed to move that file to
> /usr/share/systemtap/tapsets/powerpc.  [...]

This was a consequence of PR4186, a change noted in NEWS for release 1.0.

  The systemtap notion of "architecture" now matches the kernel's, rather
  than that of "uname -m".  This means that 32-bit i386 family are all
  known as "i386" rather than "i386" or "i686"; "ppc64" as "powerpc";
  "s390x" as "s390", and so on.  This is consistent between the new
  "-a ARCH" flag and the script-level %( arch ... %) conditional.

If you don't want to move stapitrace over to the new conventions, you
could put your tapset file under /usr/share/systemtap/tapset directly,
and guard it with  %( arch == "powerpc" || arch == "ppc64" %? .... %)


- FChE


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]