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.7-239-g07c9d78 Date: Mon, 21 May 2012 10:59:00 -0000 [thread overview] Message-ID: <20120521105951.28736.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 07c9d78ebb28b888f01aed9c206e724f0e72db25 (commit) from 4e8c02766b4199adc3219e4fa41433fe7452a305 (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 07c9d78ebb28b888f01aed9c206e724f0e72db25 Author: Mark Wielaard <mjw@redhat.com> Date: Mon May 21 12:57:41 2012 +0200 Add testcase for PR14107 Bad user unwinding from kernel fatal signal handler. This is really a kernel bug, see bug report, when the CFI for the assembly code is missing we cannot properly recover the register state for the user process and might give a bad/missing user backtrace. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/bad-code.c | 24 ++++++++++++++++++ testsuite/systemtap.base/bad-code.exp | 44 +++++++++++++++++++++++++++++++++ testsuite/systemtap.base/bad-code.stp | 6 ++++ 3 files changed, 74 insertions(+), 0 deletions(-) create mode 100644 testsuite/systemtap.base/bad-code.c create mode 100644 testsuite/systemtap.base/bad-code.exp create mode 100644 testsuite/systemtap.base/bad-code.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-05-21 10: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=20120521105951.28736.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).