| Summary: | stap unable to resolve probe points for 32 bit user space apps on PPC64 arch. | ||
|---|---|---|---|
| Product: | systemtap | Reporter: | Srikar Dronamraju <srikar> |
| Component: | translator | Assignee: | Unassigned <systemtap> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Attachments: | proposed fix | ||
Created attachment 3003 [details] proposed fix Srikar, could you please see if this fixes the problem? > However a 64 bit bz6850 does seem to face the same problem. Is this a typo? s/does/doesn't/, per Srikar's 10/8/08 comment on bug 6850? > > Srikar, could you please see if this fixes the problem? Verified that this patch fixes the problem of tracing 32 bit user applications. > > > However a 64 bit bz6850 does seem to face the same problem. > Is this a typo? s/does/doesn't/, per Srikar's 10/8/08 comment on bug 6850? Yes that was a typo from my end. Indicated fix checked in: commit 7635926 |
While trying to run testsuite/systemtap.base/bz6850.stp on powerpc machine, stap errors out. Here are the details. #file bz6850 ./bz6850: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped # stap -v -v -v bz6850.stp SystemTap translator/driver (version 0.7.1/0.137 git branch origin_master, commit 5311c037 + changes) Copyright (C) 2005-2008 Red Hat, Inc. and others This is free software; see the source for copying conditions. Session arch: ppc64 release: 2.6.23 Created temporary directory "/tmp/stapceaG4O" Searched '/usr/local/share/systemtap/tapset/ppc64/*.stp', found 2 Searched '/usr/local/share/systemtap/tapset/*.stp', found 43 Pass 1: parsed user script and 45 library script(s) in 430usr/10sys/501real ms. parsed '*' -> func '*' semantic error: ELF machine ppc (code 20) mismatch with target ppc64 in '/home/srikar/work/git.systemtap/testsuite/systemtap.base/bz6850' semantic error: no match while resolving probe point process("./bz6850").function("*").call parsed '*' -> func '*' semantic error: no match while resolving probe point process("./bz6850").function("*").return semantic error: no probes found Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 0usr/0sys/8real ms. Pass 2: analysis failed. Try again with more '-v' (verbose) options. Running rm -rf /tmp/stapceaG4O However a 64 bit bz6850 does seem to face the same problem.