[Feature] Systemtap probes supoort on ppc64LE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemtap (Ubuntu) |
Fix Released
|
High
|
Adam Conrad | ||
Wily |
Fix Released
|
High
|
Adam Conrad |
Bug Description
== Comment: #0 ==
Systemtap isn't able to get any hit on most of the kernel and user space functions on ppc64 LE. PPC64 ELF ABI v2 has a Global entry point and a local entry point for the functions. We need the Local entry point in order to probe these functions. However, the DIE for these functions in debuginfo return the function.entrypc which is same as the global entry point. The local entry point is not encoded in the debuginfo of the ELFs. The offset to local entry point is however encoded in the st_other field of these symbols in the symbol table.
We need to use this field to adjust the sym.st_value to actually point to the local entry point instead of the global entry point.
The patches are already merged with upstream systemtap. Here are the links to the patches :
https:/
https:/
https:/
tags: | added: architecture-ppc64le bugnameltc-126987 severity-high targetmilestone-inin1510 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1486352/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]