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] Use gdbpy_enter in python.c
Date: Wed, 11 Jan 2017 14:43:00 -0000 [thread overview]
Message-ID: <60e600ec691255536ae53e365d0410ecf79bdea2@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 60e600ec691255536ae53e365d0410ecf79bdea2 ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 60e600ec691255536ae53e365d0410ecf79bdea2
Use gdbpy_enter in python.c
Change the simple parts of python.c to use gdbpy_enter.
2017-01-10 Tom Tromey <tom@tromey.com>
* python/python.c (gdbpy_eval_from_control_command)
(gdbpy_source_script, gdbpy_run_events)
(gdbpy_source_objfile_script, gdbpy_execute_objfile_script)
(gdbpy_free_type_printers, gdbpy_finish_initialization): Use
gdbpy_enter.
next reply other threads:[~2017-01-11 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 14:43 sergiodj+buildbot [this message]
2017-01-11 14:43 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-01-11 22:18 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-01-11 22:19 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-11 22:33 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-01-11 22:47 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-01-11 22:56 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-01-11 23:05 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-01-11 23:29 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-01-12 6:31 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-12 7:21 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2017-01-12 9:02 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2017-01-12 9:31 ` Failures on Debian-i686, " sergiodj+buildbot
2017-01-14 15:07 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-01-14 16:11 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-14 17:21 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2017-01-15 2:45 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-01-15 3:49 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2017-01-15 5:32 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-01-15 6:12 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2017-01-11 20:35 [binutils-gdb] Use gdbpy_enter in python.c 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=60e600ec691255536ae53e365d0410ecf79bdea2@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: 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).