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] remote.c, QCatchSyscalls: Build std::string instead of unique_xmalloc_ptr
Date: Mon, 30 Oct 2017 13:20:00 -0000 [thread overview]
Message-ID: <1b81856f5b00e7ba860e4de2f3a426f342327165@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 1b81856f5b00e7ba860e4de2f3a426f342327165 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 1b81856f5b00e7ba860e4de2f3a426f342327165
remote.c, QCatchSyscalls: Build std::string instead of unique_xmalloc_ptr
Simplify the code a little bit using std::string + string_appendf.
gdb/ChangeLog:
2017-10-30 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@ericsson.com>
* remote.c (remote_set_syscall_catchpoint): Build a std::string
instead of a gdb::unique_xmalloc_ptr, using string_appendf.
next reply other threads:[~2017-10-30 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 13:20 sergiodj+buildbot [this message]
2017-10-30 13:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-30 14:55 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-30 14:58 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-30 15:38 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-30 16:05 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-30 16:21 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-30 16:22 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-10-30 16:37 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-10-30 16:42 ` Failures on Fedora-x86_64-native-extended-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=1b81856f5b00e7ba860e4de2f3a426f342327165@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).