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, master, updated. release-1.6-381-g756df9f Date: Fri, 04 Nov 2011 16:29:00 -0000 [thread overview] Message-ID: <20111104162903.30159.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 756df9f5d5bc9f9e9a2cbfaffadcab9895a8b1e2 (commit) from 63334faa5f09f858a83affc8f5d65aa971779b40 (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 756df9f5d5bc9f9e9a2cbfaffadcab9895a8b1e2 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Nov 4 17:26:43 2011 +0100 PPC64 Dwarf handle both .debug_frame and .eh_frame register mappings. These are slightly strange since they don't really use dwarf register mappings, but gcc internal register numbers. There is some confusion about the numbering see http://gcc.gnu.org/ml/gcc/2004-01/msg00025.html We just handle the 32 fixed point registers, mq, count and link and ignore status registers, floating point, vectors and special registers (most of which aren't available in pt_regs anyway). Also we placed nip last since we use that as UNW_PC register and it needs to be filled in. Note that we handle both the .eh_frame and .debug_frame numbering at the same time. There is potential overlap though. 64 maps to cr in one and mq in the other... ----------------------------------------------------------------------- Summary of changes: runtime/unwind/ppc64.h | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-04 16:29 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=20111104162903.30159.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).