public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: tromey@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-sergiodj-stap: check for stap probe in unwinder Date: Tue, 15 Mar 2011 20:41:00 -0000 [thread overview] Message-ID: <20110315204143.25772.qmail@sourceware.org> (raw) The branch, archer-sergiodj-stap has been updated via 05d6ff701153e1d819de3105800ccf517d5102b7 (commit) from e54d21757a87c22d7c3f0119ccc11aa1f4d0a4a4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- commit 05d6ff701153e1d819de3105800ccf517d5102b7 Author: Tom Tromey <tromey@redhat.com> Date: Tue Mar 15 14:41:21 2011 -0600 check for stap probe in unwinder ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/gdb.cp/nextoverthrow.exp | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) First 500 lines of diff: diff --git a/gdb/testsuite/gdb.cp/nextoverthrow.exp b/gdb/testsuite/gdb.cp/nextoverthrow.exp index 89c02d6..a970bb9 100644 --- a/gdb/testsuite/gdb.cp/nextoverthrow.exp +++ b/gdb/testsuite/gdb.cp/nextoverthrow.exp @@ -53,6 +53,17 @@ gdb_test_multiple "print _Unwind_DebugHook" "check for unwinder hook" { } } if {!$ok} { + gdb_test_multiple "info probe" "check for stap probe in unwinder" { + -re ".*libgcc.*unwind.*\r\n$gdb_prompt $" { + pass "check for stap probe in unwinder" + set ok 1 + } + -re "\r\n$gdb_prompt $" { + } + } +} + +if {!$ok} { unsupported "nextoverthrow.exp could not find _Unwind_DebugHook" return -1 } hooks/post-receive -- Repository for Project Archer.
reply other threads:[~2011-03-15 20:41 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=20110315204143.25772.qmail@sourceware.org \ --to=tromey@sourceware.org \ --cc=archer-commits@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).