public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Return EXT_LANG_BT_ERROR in one more spot in py-framefilter.c Date: Tue, 27 Mar 2018 07:57:00 -0000 [thread overview] Message-ID: <1f111921a0f8e3f62a19808349ff9bcbd4e54043@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 1f111921a0f8e3f62a19808349ff9bcbd4e54043 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 1f111921a0f8e3f62a19808349ff9bcbd4e54043 Return EXT_LANG_BT_ERROR in one more spot in py-framefilter.c While reading py-framefilter.c, I found one spot where an exception could be caught but then not be turned into EXT_LANG_BT_ERROR. This patch fixes this spot. gdb/ChangeLog 2018-03-26 Tom Tromey <tom@tromey.com> * python/py-framefilter.c (py_print_single_arg): Return EXT_LANG_BT_ERROR from catch.
next reply other threads:[~2018-03-27 7:57 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-27 7:57 sergiodj+buildbot [this message] 2018-03-27 7:57 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-03-27 11:48 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-27 12:03 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-27 12:17 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-03-27 12:55 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-27 13:00 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-27 13:04 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-27 13:17 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-27 13:19 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-27 13:36 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-27 16:49 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-27 17:20 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
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=1f111921a0f8e3f62a19808349ff9bcbd4e54043@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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).