public inbox for archer-commits@sourceware.org help / color / mirror / Atom feed
From: jkratoch@sourceware.org To: archer-commits@sourceware.org Subject: [SCM] archer-jankratochvil-python: Merge commit 'origin/archer-tromey-python' into archer-jankratochvil-python Date: Fri, 06 Mar 2009 16:59:00 -0000 [thread overview] Message-ID: <20090306165905.6365.qmail@sourceware.org> (raw) The branch, archer-jankratochvil-python has been updated via ed5683b8c1957677e95baa80db811894c39a321e (commit) via 7479ac4e385bcaa2846c3aad5c616f571ff53c97 (commit) from 652968509fe26811de7e57036ec8bd801593ccbb (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email. - Log ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: gdb/testsuite/gdb.python/python-frame.exp | 17 +++-------------- 1 files changed, 3 insertions(+), 14 deletions(-) First 500 lines of diff: diff --git a/gdb/testsuite/gdb.python/python-frame.exp b/gdb/testsuite/gdb.python/python-frame.exp index e9e063a..674c25e 100644 --- a/gdb/testsuite/gdb.python/python-frame.exp +++ b/gdb/testsuite/gdb.python/python-frame.exp @@ -81,20 +81,9 @@ gdb_test "python print 'result =', f0.pc ()" " = \[0-9\]+" "test Frame.pc" gdb_test "python print 'result =', f0.addr_in_block ()" " = \[0-9\]+" "test Frame.addr_in_block" gdb_test "python print 'result =', f0.older ().equals (f1)" " = True" "test Frame.older" gdb_test "python print 'result =', f1.newer ().equals (f0)" " = True" "test Frame.newer" - -set test "test Frame.read_var - error" -gdb_test_multiple "python print 'result =', f0.read_var ('b')" $test { - -re "ValueError: variable 'b' not found.*Error while executing Python code.\r\n$gdb_prompt $" { - pass $test - } - -re "result = \\\{i = \\\{0, \[0-9\]+\\\}, d = 0\\.\[0-9\]+\\\}\r\n$gdb_prompt $" { - # libm.so debuginfo contains file static symbol `b' from `atnat.h'. - # local `b' would be find first if it would exist so it is more a PASS. - setup_xfail *-*-* - fail $test - } -} - +gdb_test "python print 'result =', f0.read_var ('variable_which_surely_doesnt_exist')" \ + "ValueError: variable 'variable_which_surely_doesnt_exist' not found.*Error while executing Python code." \ + "test Frame.read_var - error" gdb_test "python print 'result =', f0.read_var ('a')" " = 1" "test Frame.read_var - success" gdb_test "python print 'result =', gdb.newest_frame ().equals (f0)" " = True" "test gdb.newest_frame" hooks/post-receive -- Repository for Project Archer.
next reply other threads:[~2009-03-06 16:59 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-06 16:59 jkratoch [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-06-26 13:51 jkratoch 2009-03-30 17:22 jkratoch 2009-03-29 22:42 jkratoch 2009-03-27 0:35 jkratoch 2009-03-25 19:00 jkratoch 2009-03-24 17:33 jkratoch 2009-03-09 17:05 jkratoch 2009-03-06 14:26 jkratoch 2009-03-05 21:53 jkratoch 2009-03-05 21:15 jkratoch 2009-03-04 23:54 jkratoch 2009-03-04 22:34 jkratoch 2009-03-04 15:02 jkratoch 2009-03-03 21:46 jkratoch 2009-03-03 21:45 jkratoch 2009-03-02 20:46 jkratoch 2009-03-01 14:38 jkratoch 2009-02-28 19:26 jkratoch 2009-02-26 23:01 jkratoch
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=20090306165905.6365.qmail@sourceware.org \ --to=jkratoch@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).