public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, mjw/backtrace, updated. release-1.5-194-g556ca99 Date: Tue, 26 Jul 2011 21:42:00 -0000 [thread overview] Message-ID: <20110726214253.32767.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, mjw/backtrace has been updated via 556ca99181aec9034dcd76072ba85e7d3d5427cc (commit) via f4eff05f664d737ece23554e9322e1f84cf20c6e (commit) from 5ad2040b40b084356021e8bbf484a98b728865b9 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 556ca99181aec9034dcd76072ba85e7d3d5427cc Author: Mark Wielaard <mjw@redhat.com> Date: Tue Jul 26 23:31:01 2011 +0200 Allow gcc to optimize away uprobe_get_pc() calls in some situations. If a call is made to the stack-x86.c __stp_stack_print() it might try to call uprobe_get_pc(). If this is just a kernel backtrace then uprobes might not be loaded. Add a hint by explicitly clearing the struct uretprobe_instance *ri variable in that cass in the calling function _stp_stack_print() in stack.c, so that gcc optimizes away the uprobe_get_pc() call, so that the symbol isn't in the module anymore. Would cause issues like: WARNING: "uprobe_get_pc" [stap_d46895_3786.ko] undefined! Error inserting module 'stap_d46895_3786.ko': Unknown symbol in module commit f4eff05f664d737ece23554e9322e1f84cf20c6e Author: Mark Wielaard <mjw@redhat.com> Date: Tue Jul 26 23:29:48 2011 +0200 Adjust expected "no backtrace" string in context/backtrace.tcl test. The new generic form is now "<no kernel backtrace at PROBEPOINT>". ----------------------------------------------------------------------- Summary of changes: runtime/stack.c | 14 +++++++++----- testsuite/systemtap.context/backtrace.tcl | 2 +- 2 files changed, 10 insertions(+), 6 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-07-26 21:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20110726214253.32767.qmail@sourceware.org \ --to=mark@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).