public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: scox@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-377-gb0683c4 Date: Fri, 10 Dec 2010 15:59:00 -0000 [thread overview] Message-ID: <20101210155933.16041.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, master has been updated via b0683c4ceb463087799895e241da5540782f196a (commit) from ac97c3f7fa0802ac19af4fe38de97b8d8f3dff83 (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 b0683c4ceb463087799895e241da5540782f196a Author: Stan Cox <scox@redhat.com> Date: Fri Dec 10 10:48:20 2010 -0500 Fix sdt probe arg qi/si fetching on 386 * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol): Use long for default precision if "N@" is missing. * sdt_misc.exp (pbtype_flags): Don't use -g for STAP_SDT_V{2,3} (V3 asm test): Fix arch detection * sdt_types.stp: Mask negative arg values. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 2 +- testsuite/systemtap.base/sdt_misc.exp | 12 ++---------- testsuite/systemtap.base/sdt_types.stp | 30 ++++++++++++++++-------------- 3 files changed, 19 insertions(+), 25 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-12-10 15:59 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=20101210155933.16041.qmail@sourceware.org \ --to=scox@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).