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 ui_file_as_string in execute_command_to_string
Date: Wed, 09 Nov 2016 05:16:00 -0000 [thread overview]
Message-ID: <db1ec11fff1a46f7046bcbd971a42632d2ea795c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT db1ec11fff1a46f7046bcbd971a42632d2ea795c ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: db1ec11fff1a46f7046bcbd971a42632d2ea795c
Use ui_file_as_string in execute_command_to_string
... and then return std::string and adjust all callers.
gdb/ChangeLog:
2016-11-08 Pedro Alves <palves@redhat.com>
* gdbcmd.h (execute_command_to_string): Now returns std::string.
(lookup_struct_elt_type): Adjust to use std::string.
* top.c (execute_command_to_string): Use ui_file_as_string and
return std::string.
* guile/guile.c (gdbscm_execute_gdb_command): Adjust to use
std::string.
* python/python.c (execute_gdb_command): Adjust to use
std::string.
next reply other threads:[~2016-11-09 4:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 5:16 sergiodj+buildbot [this message]
2016-11-09 5:16 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2016-11-09 10:41 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-09 11:33 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-11-14 17:15 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-11-14 18:27 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-11-16 8:41 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-11-16 12:33 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " 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=db1ec11fff1a46f7046bcbd971a42632d2ea795c@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).