public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Test results for commit 5dea9fe2285fee5d53691856750a0c8960fca04d on branch gdb-7.9-branch
Date: Wed, 11 Feb 2015 15:42:00 -0000 [thread overview]
Message-ID: <5dea9fe2285fee5d53691856750a0c8960fca04d@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT 5dea9fe2285fee5d53691856750a0c8960fca04d ***
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Branch: gdb-7.9-branch
Commit: 5dea9fe2285fee5d53691856750a0c8960fca04d
framefilter quit: Make it exception safe
gdb/ChangeLog
2015-02-11 Jan Kratochvil <jan.kratochvil@redhat.com>
* python/py-framefilter.c (py_print_frame): Mention RETURN_QUIT in
function comment. Wrap all function that can throw in cleanups.
(gdbpy_apply_frame_filter): Wrap all function that can throw in
cleanups.
next reply other threads:[~2015-02-11 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 15:42 sergiodj [this message]
2015-02-11 15:42 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj
2015-02-11 15:45 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj
2015-02-11 15:45 ` Failures on Fedora-ppc64le-m64, " sergiodj
2015-02-11 15:45 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj
2015-02-12 2:50 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj
2015-02-12 3:29 ` Failures on Fedora-ppc64be-m64, " sergiodj
2015-02-12 3:55 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj
2015-02-12 4:18 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj
2015-02-12 12:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-12 12:34 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj
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=5dea9fe2285fee5d53691856750a0c8960fca04d@kwanyin \
--to=sergiodj@redhat.com \
--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: link
Be 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).